Vulnerabilities in pkg:pypi/cdo-local-uuid

PACKAGE
Advisory Identifier: GHSA-rgrf-6mf5-m882
Advisory Summary

CVE-2024-22194 is a LOW (CVSS 2.2) cdo-local-uuid vulnerable to insertion of vulnerability (CWE-337: Predictable Seed in Pseudo-Random Number Generator (PRNG)) affecting Cdo local uuid libraries in the PyPI ecosystem. The issue involves cdo-local-uuid vulnerable to insertion of artifact derived from developer's present working directory into demonstration code. Remediation is available by upgrading affected packages to version 0.5.0, 0.5.1, 0.6.1, 0.7.1, 0.8.1, 0.9.1, 0.10.1, 0.11.1, 0.12.1, 0.13.1, 0.14.1.

1 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:pypi/cdo-local-uuid

1 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:pypi/cdo-local-uuid. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-rgrf-6mf5-m882 CVE-2024-22194 LOW cdo-local-uuid vulnerable to insertion of artifact derived from developer's Present Working Directory into demonstration code

CVE-2024-22194 at a Glance

CVE Identifier CVE-2024-22194
GHSA Identifier GHSA-rgrf-6mf5-m882
Severity LOW
CVSS v3.1 Base Score 2.2
CWE Classification CWE-337: Predictable Seed in Pseudo-Random Number Generator (PRNG)
Affected Product Cdo local uuid
Package Ecosystem PyPI
Published Date
Last Updated

Security Impact

CVSS: 2.2

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:N/A:N).

Attack Vector Local (AV:L)
Attack Complexity High (AC:H)
Privileges Required Low (PR:L)
User Interaction Required (UI:R)
Scope Unchanged (S:U)
Confidentiality Low (C:L)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2024-22194

To remediate this vulnerability, upgrade all affected Cdo local uuid dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

cdo-local-uuid fixed: 0.5.0
pip install cdo-local-uuid>=0.5.0
case-utils fixed: 0.5.1
pip install case-utils>=0.5.1
case-utils fixed: 0.6.1
pip install case-utils>=0.6.1
case-utils fixed: 0.7.1
pip install case-utils>=0.7.1
case-utils fixed: 0.8.1
pip install case-utils>=0.8.1
case-utils fixed: 0.9.1
pip install case-utils>=0.9.1
case-utils fixed: 0.10.1
pip install case-utils>=0.10.1
case-utils fixed: 0.11.1
pip install case-utils>=0.11.1
case-utils fixed: 0.12.1
pip install case-utils>=0.12.1
case-utils fixed: 0.13.1
pip install case-utils>=0.13.1
case-utils fixed: 0.14.1
pip install case-utils>=0.14.1
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

pip show cdo-local-uuid

How to Check if You Are Affected

To determine whether your Python environment is affected by CVE-2024-22194, inspect your installed packages using pip:

pip show cdo-local-uuid

Analyze the terminal output to locate any version of Cdo local uuid in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.5.0), your application is affected.

Note: The pip show cdo-local-uuid command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-337: Predictable Seed in Pseudo-Random Number Generator (PRNG), where a pseudo-random number generator (prng) is initialized from a predictable seed, such as the process id or system time. In Cdo local uuid, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact _What kind of vulnerability is it? Who is impacted?_ An information leakage vulnerability is present in [`cdo-local-uuid`](https://pypi.org/project/cdo-local-uuid/) at version `0.4.0`, and in [`case-utils`](https://pypi.org/project/case-utils/) in unpatched versions (matching the pattern `0.x.0`) at and since `0.5.0`, before `0.15.0`. The vulnerability stems from a Python function, `cdo_local_uuid.local_uuid()`, and its original implementation `case_utils.local_uuid()`. Henceforth, both will be called `local_uuid()`. `local_uuid()` generates UUIDv5s using a deterministic pseudorandom number stream. This was written to make graph application demonstrations generate consistent, version-controllable output with minimal noise caused by demonstration re-runs. Part of the information used to keep individual examples' generated output distinct from one another is seed information from the caller's environment, particularly the program's argument vector. The present working directory is also included as part of the seed information, but for reasons including maintaining user environment privacy, as well as keeping generated identifiers consistent regardless of where a source tree is housed on a user's file system, the present working directory is trimmed from the left to exclude path information outside of a supplied "Top" source directory. (In context of the Make scripting language, this "top" directory is typically in a variable called `top_srcdir`. In context of Git-based project management, this directory is expected to be the root directory of a freshly "Cloned" project, e.g., where `.git` is stored.) Under certain conditions, a user's present working directory, as an absolute path, was incorporated into seed data for the `local_uuid()` deterministic pseudorandom number stream. This violates an expectation made in the documented purpose of the `local_uuid()` function, and leaks information about a calling user's environment. The conditions are: * Given a project with top source directory `top_srcdir`, for instance `/home/user1/Documents/Project1`; * Given a Python script housed directly in `top_srcdir`, for instance at `${top_srcdir}/example.py`, written to support the deterministic mode of `local_uuid()`; * Given a call to that Python script that follows the documentation for `local_uuid()`; The absolute path for `top_srcdir` was then included in the seed information for the UUIDv5 stream, when what was intended was a relative path spelling. That is, instead of `./example.py` being in the seed data, `/home/user1/Documents/Project1/example.py` was in the seed data. This does not leak the present working directory directly. But, given other knowledge of how a program had been called to generate data using `local_uuid()` under these conditions, it becomes possible to determine that a chosen path can lead to a known UUIDv5 value. Note that it is not necessarily knowable that the chosen path is the *only* solution to a sequence reconstruction; but, the path can be confirmed to be *a* solution. ### Patches _Has the problem been patched? What versions should users upgrade to?_ The issue has been patched, in the `cdo-local-uuid` source repository and the `case-utils` source repository. Users should upgrade to any of these versions minimally: * `case-utils == 0.5.1` * `case-utils == 0.6.1` * `case-utils == 0.7.1` * `case-utils == 0.8.1` * `case-utils == 0.9.1` * `case-utils == 0.10.1` * `case-utils == 0.11.1` * `case-utils == 0.12.1` * `case-utils == 0.13.1` * `case-utils == 0.14.1` * `case-utils >= 0.15.0` * `cdo-local-uuid == 0.5.0` All `case-utils` releases that contain the patch have the commit `ea630cce66b26dae6d7fa7e02451d6e25456a5f2` in their Git history. Anyone interested in confirming the presence of this commit in a certain branch or tag can run the following test (written in Bash), substituting the desired branch name for the assigned value of `my_git_ref_of_interest`: ```bash #!/bin/bash # Present working directory ($PWD) should be in a clone of this repository: # https://github.com/casework/CASE-Utilities-Python my_git_ref_of_interest=main test \ "xea630cce66b26dae6d7fa7e02451d6e25456a5f2" \ == \ "x$(git merge-base ea630cc ${my_git_ref_of_interest})" echo $? # Should print '0' ``` Note that other releases have been posted atop some of those minimal versions recommended for upgrading, named, e.g., `0.5.1.post0`. These releases were posted to update internal library version numbers, and otherwise contain no functional changes, in accordance with Python Packaging guidance: * https://packaging.python.org/en/latest/specifications/version-specifiers/#post-release-separators ### Workarounds _Is there a way for users to fix or remediate the vulnerability without upgrading?_ If the script calling `cdo_local_uuid.local_uuid()` is moved out of the "Top" source directory, the issue is addressed. ### References _Are there any links users can visit to find out more?_ The issue is addressed in this Pull Request: * https://github.com/Cyber-Domain-Ontology/CDO-Utility-Local-UUID/pull/3 Tests to reproduce the issue's conditions and confirm it has been addressed are in this Pull Requested: * https://github.com/Cyber-Domain-Ontology/CDO-Utility-Local-UUID/pull/4 <!-- CVSS3.1 vector determined by rubric diagrams at this page: https://www.first.org/cvss/v3.1/user-guide -->

CVE-2024-22194 Affected Cdo local uuid Versions

11 component(s)
Fixed Versions:
0.5.00.5.10.6.10.7.10.8.10.9.10.10.10.11.10.12.10.13.10.14.1
Product / Package Ecosystem Affected Versions Fixed Version
cdo-local-uuid
PyPI
≥ 0.4.0
< 0.5.0
All 1 versions
0.4.0
0.5.0
case-utils
PyPI
≥ 0.5.0
< 0.5.1
All 1 versions
0.5.0
0.5.1
case-utils
PyPI
≥ 0.6.0
< 0.6.1
All 1 versions
0.6.0
0.6.1
case-utils
PyPI
≥ 0.7.0
< 0.7.1
All 1 versions
0.7.0
0.7.1
case-utils
PyPI
≥ 0.8.0
< 0.8.1
All 1 versions
0.8.0
0.8.1
case-utils
PyPI
≥ 0.9.0
< 0.9.1
All 1 versions
0.9.0
0.9.1
case-utils
PyPI
≥ 0.10.0
< 0.10.1
All 1 versions
0.10.0
0.10.1
case-utils
PyPI
≥ 0.11.0
< 0.11.1
All 1 versions
0.11.0
0.11.1
case-utils
PyPI
≥ 0.12.0
< 0.12.1
All 1 versions
0.12.0
0.12.1
case-utils
PyPI
≥ 0.13.0
< 0.13.1
All 1 versions
0.13.0
0.13.1
case-utils
PyPI
≥ 0.14.0
< 0.14.1
All 1 versions
0.14.0
0.14.1

References

GitHub Advisory / Wiki ADVISORY
https://github.com/Cyber-Domain-Ontology/CDO-Utility-Local-UUID/security/advisories/GHSA-rgrf-6mf5-m882
NVD — CVE-2024-22194 NVD
https://nvd.nist.gov/vuln/detail/CVE-2024-22194
Cdo local uuid Source Repository REPOSITORY
https://github.com/Cyber-Domain-Ontology/CDO-Utility-Local-UUID/pull/3
Cdo local uuid Source Repository REPOSITORY
https://github.com/Cyber-Domain-Ontology/CDO-Utility-Local-UUID/pull/4
Security Fix Commit FIX COMMIT
https://github.com/casework/CASE-Utilities-Python/commit/fdc32414eccfcbde6be0fd91b7f491cc0779b02d#diff-e60b9cb8fb480ed27283a030a0898be3475992d78228f4045b12ce5cbb2f0509
Security Fix Commit FIX COMMIT
https://github.com/casework/CASE-Utilities-Python/commit/fca7388f09feccd3b9ea88e6df9c7a43a5349452
Security Fix Commit FIX COMMIT
https://github.com/casework/CASE-Utilities-Python/commit/e4ffadc3d56fd303b8f465d727c4a58213d311a1
Security Fix Commit FIX COMMIT
https://github.com/casework/CASE-Utilities-Python/commit/db428a0745dac4fdd888ced9c52f617695519f9d
Security Fix Commit FIX COMMIT
https://github.com/casework/CASE-Utilities-Python/commit/939775f956796d0432ecabbf62782ed7ad1007b5
Security Fix Commit FIX COMMIT
https://github.com/casework/CASE-Utilities-Python/commit/80551f49241c874c7c50e14abe05c5017630dad2
Security Fix Commit FIX COMMIT
https://github.com/casework/CASE-Utilities-Python/commit/7e02d18383eabbeb9fb4ec97d81438c9980a4790
Security Fix Commit FIX COMMIT
https://github.com/casework/CASE-Utilities-Python/commit/5acb929dfb599709d1c8c90d1824dd79e0fd9e10
Security Fix Commit FIX COMMIT
https://github.com/casework/CASE-Utilities-Python/commit/1cccae8eb3cf94b3a28f6490efa0fbf5c82ebd6b
Cdo local uuid Source Repository REPOSITORY
https://github.com/Cyber-Domain-Ontology/CDO-Utility-Local-UUID
Security Fix Commit FIX COMMIT
https://github.com/casework/CASE-Utilities-Python/commit/00864cd12de7c50d882dd1a74915d32e939c25f9
Security Fix Commit FIX COMMIT
https://github.com/Cyber-Domain-Ontology/CDO-Utility-Local-UUID/commit/9e78f7cb1075728d0aafc918514f32a1392cd235
Cdo local uuid Source Repository REPOSITORY
https://github.com/pypa/advisory-database/tree/main/vulns/case-utils/PYSEC-2024-5.yaml
Cdo local uuid Source Repository REPOSITORY
https://github.com/pypa/advisory-database/tree/main/vulns/cdo-local-uuid/PYSEC-2024-6.yaml

Frequently Asked Questions

What is CVE-2024-22194?
CVE-2024-22194 is a security vulnerability in Cdo local uuid involving cdo-local-uuid vulnerable to insertion of artifact derived from developer's Present Working Directory into demonstration code under CWE-337: Predictable Seed in Pseudo-Random Number Generator (PRNG).
Which Cdo local uuid versions are affected?
Affected versions include releases prior to 0.5.0, 0.5.1, 0.6.1, 0.7.1, 0.8.1, 0.9.1, 0.10.1, 0.11.1, 0.12.1, 0.13.1, 0.14.1 across affected packages: cdo-local-uuid, case-utils.
What version fixes CVE-2024-22194?
Upgrading to 0.5.0, 0.5.1, 0.6.1, 0.7.1, 0.8.1, 0.9.1, 0.10.1, 0.11.1, 0.12.1, 0.13.1, 0.14.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is cdo-local-uuid affected?
Yes, cdo-local-uuid is affected in releases prior to 0.5.0. Upgrade your dependency to 0.5.0 or later.
Is case-utils affected?
Yes, case-utils is affected in releases prior to 0.5.1, 0.6.1, 0.7.1, 0.8.1, 0.9.1, 0.10.1, 0.11.1, 0.12.1, 0.13.1, 0.14.1. Upgrade your dependency to 0.5.1, 0.6.1, 0.7.1, 0.8.1, 0.9.1, 0.10.1, 0.11.1, 0.12.1, 0.13.1, 0.14.1 or later.
What is the CVSS score of CVE-2024-22194?
CVE-2024-22194 has a CVSS v3.1 base score of 2.2 (LOW) with vector string CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:N/A:N.
What CWE is associated with CVE-2024-22194?
CVE-2024-22194 is classified under CWE-337: Predictable Seed in Pseudo-Random Number Generator (PRNG) (A Pseudo-Random Number Generator (PRNG) is initialized from a predictable seed, such as the process ID or system time.).
How can I check PyPI dependencies for CVE-2024-22194?
Run the dependency tree command: 'pip show cdo-local-uuid'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-rgrf-6mf5-m882",
  "modified" : "2024-09-13T17:39:18Z",
  "published" : "2024-01-11T15:18:51Z",
  "aliases" : [ "CVE-2024-22194" ],
  "summary" : "cdo-local-uuid vulnerable to insertion of artifact derived from developer's Present Working Directory into demonstration code",
  "details" : "### Impact\n_What kind of vulnerability is it? Who is impacted?_\n\nAn information leakage vulnerability is present in [`cdo-local-uuid`](https://pypi.org/project/cdo-local-uuid/) at version `0.4.0`, and in [`case-utils`](https://pypi.org/project/case-utils/) in unpatched versions (matching the pattern `0.x.0`) at and since `0.5.0`, before `0.15.0`.\n\nThe vulnerability stems from a Python function, `cdo_local_uuid.local_uuid()`, and its original implementation `case_utils.local_uuid()`.  Henceforth, both will be called `local_uuid()`.\n\n`local_uuid()` generates UUIDv5s using a deterministic pseudorandom number stream.  This was written to make graph application demonstrations generate consistent, version-controllable output with minimal noise caused by demonstration re-runs.  Part of the information used to keep individual examples' generated output distinct from one another is seed information from the caller's environment, particularly the program's argument vector.  The present working directory is also included as part of the seed information, but for reasons including maintaining user environment privacy, as well as keeping generated identifiers consistent regardless of where a source tree is housed on a user's file system, the present working directory is trimmed from the left to exclude path information outside of a supplied \"Top\" source directory.  (In context of the Make scripting language, this \"top\" directory is typically in a variable called `top_srcdir`.  In context of Git-based project management, this directory is expected to be the root directory of a freshly \"Cloned\" project, e.g., where `.git` is stored.)\n\nUnder certain conditions, a user's present working directory, as an absolute path, was incorporated into seed data for the `local_uuid()` deterministic pseudorandom number stream.  This violates an expectation made in the documented purpose of the `local_uuid()` function, and leaks information about a calling user's environment.\n\nThe conditions are:\n\n* Given a project with top source directory `top_srcdir`, for instance `/home/user1/Documents/Project1`;\n* Given a Python script housed directly in `top_srcdir`, for instance at `${top_srcdir}/example.py`, written to support the deterministic mode of `local_uuid()`;\n* Given a call to that Python script that follows the documentation for `local_uuid()`;\n\nThe absolute path for `top_srcdir` was then included in the seed information for the UUIDv5 stream, when what was intended was a relative path spelling.  That is, instead of `./example.py` being in the seed data, `/home/user1/Documents/Project1/example.py` was in the seed data.\n\nThis does not leak the present working directory directly.  But, given other knowledge of how a program had been called to generate data using `local_uuid()` under these conditions, it becomes possible to determine that a chosen path can lead to a known UUIDv5 value.  Note that it is not necessarily knowable that the chosen path is the *only* solution to a sequence reconstruction; but, the path can be confirmed to be *a* solution.\n\n\n### Patches\n_Has the problem been patched? What versions should users upgrade to?_\n\nThe issue has been patched, in the `cdo-local-uuid` source repository and the `case-utils` source repository.\n\nUsers should upgrade to any of these versions minimally:\n\n* `case-utils == 0.5.1`\n* `case-utils == 0.6.1`\n* `case-utils == 0.7.1`\n* `case-utils == 0.8.1`\n* `case-utils == 0.9.1`\n* `case-utils == 0.10.1`\n* `case-utils == 0.11.1`\n* `case-utils == 0.12.1`\n* `case-utils == 0.13.1`\n* `case-utils == 0.14.1`\n* `case-utils >= 0.15.0`\n* `cdo-local-uuid == 0.5.0`\n\nAll `case-utils` releases that contain the patch have the commit `ea630cce66b26dae6d7fa7e02451d6e25456a5f2` in their Git history.  Anyone interested in confirming the presence of this commit in a certain branch or tag can run the following test (written in Bash), substituting the desired branch name for the assigned value of `my_git_ref_of_interest`:\n\n```bash\n#!/bin/bash\n# Present working directory ($PWD) should be in a clone of this repository:\n# https://github.com/casework/CASE-Utilities-Python\nmy_git_ref_of_interest=main\ntest \\\n  \"xea630cce66b26dae6d7fa7e02451d6e25456a5f2\" \\\n  == \\\n  \"x$(git merge-base ea630cc ${my_git_ref_of_interest})\"\necho $?  # Should print '0'\n```\n\nNote that other releases have been posted atop some of those minimal versions recommended for upgrading, named, e.g., `0.5.1.post0`.  These releases were posted to update internal library version numbers, and otherwise contain no functional changes, in accordance with Python Packaging guidance:\n\n* https://packaging.python.org/en/latest/specifications/version-specifiers/#post-release-separators\n\n\n### Workarounds\n_Is there a way for users to fix or remediate the vulnerability without upgrading?_\n\nIf the script calling `cdo_local_uuid.local_uuid()` is moved out of the \"Top\" source directory, the issue is addressed.\n\n\n### References\n_Are there any links users can visit to find out more?_\n\nThe issue is addressed in this Pull Request:\n\n* https://github.com/Cyber-Domain-Ontology/CDO-Utility-Local-UUID/pull/3\n\nTests to reproduce the issue's conditions and confirm it has been addressed are in this Pull Requested:\n\n* https://github.com/Cyber-Domain-Ontology/CDO-Utility-Local-UUID/pull/4\n\n<!--\nCVSS3.1 vector determined by rubric diagrams at this page:\nhttps://www.first.org/cvss/v3.1/user-guide\n-->",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:N/A:N"
  }, {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:U"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "cdo-local-uuid"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.4.0"
      }, {
        "fixed" : "0.5.0"
      } ]
    } ],
    "versions" : [ "0.4.0" ]
  }, {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "case-utils"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.5.0"
      }, {
        "fixed" : "0.5.1"
      } ]
    } ],
    "versions" : [ "0.5.0" ]
  }, {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "case-utils"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.6.0"
      }, {
        "fixed" : "0.6.1"
      } ]
    } ],
    "versions" : [ "0.6.0" ]
  }, {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "case-utils"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.7.0"
      }, {
        "fixed" : "0.7.1"
      } ]
    } ],
    "versions" : [ "0.7.0" ]
  }, {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "case-utils"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.8.0"
      }, {
        "fixed" : "0.8.1"
      } ]
    } ],
    "versions" : [ "0.8.0" ]
  }, {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "case-utils"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.9.0"
      }, {
        "fixed" : "0.9.1"
      } ]
    } ],
    "versions" : [ "0.9.0" ]
  }, {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "case-utils"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.10.0"
      }, {
        "fixed" : "0.10.1"
      } ]
    } ],
    "versions" : [ "0.10.0" ]
  }, {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "case-utils"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.11.0"
      }, {
        "fixed" : "0.11.1"
      } ]
    } ],
    "versions" : [ "0.11.0" ]
  }, {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "case-utils"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.12.0"
      }, {
        "fixed" : "0.12.1"
      } ]
    } ],
    "versions" : [ "0.12.0" ]
  }, {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "case-utils"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.13.0"
      }, {
        "fixed" : "0.13.1"
      } ]
    } ],
    "versions" : [ "0.13.0" ]
  }, {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "case-utils"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.14.0"
      }, {
        "fixed" : "0.14.1"
      } ]
    } ],
    "versions" : [ "0.14.0" ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/Cyber-Domain-Ontology/CDO-Utility-Local-UUID/security/advisories/GHSA-rgrf-6mf5-m882"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2024-22194"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/Cyber-Domain-Ontology/CDO-Utility-Local-UUID/pull/3"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/Cyber-Domain-Ontology/CDO-Utility-Local-UUID/pull/4"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/casework/CASE-Utilities-Python/commit/fdc32414eccfcbde6be0fd91b7f491cc0779b02d#diff-e60b9cb8fb480ed27283a030a0898be3475992d78228f4045b12ce5cbb2f0509"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/casework/CASE-Utilities-Python/commit/fca7388f09feccd3b9ea88e6df9c7a43a5349452"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/casework/CASE-Utilities-Python/commit/e4ffadc3d56fd303b8f465d727c4a58213d311a1"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/casework/CASE-Utilities-Python/commit/db428a0745dac4fdd888ced9c52f617695519f9d"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/casework/CASE-Utilities-Python/commit/939775f956796d0432ecabbf62782ed7ad1007b5"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/casework/CASE-Utilities-Python/commit/80551f49241c874c7c50e14abe05c5017630dad2"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/casework/CASE-Utilities-Python/commit/7e02d18383eabbeb9fb4ec97d81438c9980a4790"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/casework/CASE-Utilities-Python/commit/5acb929dfb599709d1c8c90d1824dd79e0fd9e10"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/casework/CASE-Utilities-Python/commit/1cccae8eb3cf94b3a28f6490efa0fbf5c82ebd6b"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/casework/CASE-Utilities-Python/commit/00864cd12de7c50d882dd1a74915d32e939c25f9"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/Cyber-Domain-Ontology/CDO-Utility-Local-UUID/commit/9e78f7cb1075728d0aafc918514f32a1392cd235"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/pypa/advisory-database/tree/main/vulns/case-utils/PYSEC-2024-5.yaml"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/pypa/advisory-database/tree/main/vulns/cdo-local-uuid/PYSEC-2024-6.yaml"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/Cyber-Domain-Ontology/CDO-Utility-Local-UUID"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-215", "CWE-337" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2024-01-11T15:18:51Z",
    "nvd_published_at" : "2024-01-11T03:15:10Z"
  }
}