CVE-2024-22194 is a low-severity (CVSS 2.2) CWE-215 vulnerability in cdo-local-uuid. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether CVE-2024-22194 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
cdo-local-uuid vulnerable to insertion of artifact derived from developer's Present Working Directory into demonstration code
Real-World Exposure
cdo-local-uuid🐍case-utils🐍case-utils🐍case-utils🐍case-utils🐍case-utils🐍case-utils🐍case-utils+3 moreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
cdo-local-uuid project provides a specialized UUID-generating function that can, on user request, cause a program to generate deterministic UUIDs. An information leakage vulnerability is present in cdo-local-uuid at version 0.4.0, and in 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().
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | cdo-local-uuid | ≥ 0.4.0&&< 0.5.0 | 0.5.0 |
| 🐍PyPI | case-utils | ≥ 0.5.0&&< 0.5.1 | 0.5.1 |
| 🐍PyPI | case-utils | ≥ 0.6.0&&< 0.6.1 | 0.6.1 |
| 🐍PyPI | case-utils | ≥ 0.7.0&&< 0.7.1 | 0.7.1 |
| 🐍PyPI | case-utils | ≥ 0.8.0&&< 0.8.1 | 0.8.1 |
| 🐍PyPI | case-utils | ≥ 0.9.0&&< 0.9.1 | 0.9.1 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for cdo-local-uuid. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update cdo-local-uuid to 0.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-22194 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2024-22194 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2024-22194. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2024-22194 in your dependencies?
O3 detects CVE-2024-22194 across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.