Security Resilience

CVE-2024-22194

Info Disclosure in Lfprojects Case Python Utilities 0.10.0 … 0.9.0

Public PoCInfo Disclosure
Published
11 January 2024
Modified
17 June 2026
Patch / advisory
View advisory
CVSS Score v3.1 2.2
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:N/A:N
EPSS Score 0.0041 34th percentile
Risk Priority 22 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2024-22194 is a low-severity Insertion of Sensitive Information Into Debugging Code (CWE-215) vulnerability in Lfprojects Case Python Utilities. Its CVSS base score is 2.2 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Data Obfuscation (T1001); ranked at the 34th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to CM-7 (Least Functionality) and SA-11 (Developer Testing and Evaluation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A04:2025 Cryptographic FailuresA10:2025 Mishandling of Exceptional Conditions

EU & UK References

Vulnerability Data

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`)…

more

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()`.

CWE(s)
CWE-215CWE-337

Related Threats

MITRE ATT&CK Enterprise Techniques

T1001 Data Obfuscation Command And Control
Adversaries may obfuscate command and control traffic to make it more difficult to detect.
attack.mitre.org →
T1001.002 Steganography Command And Control
Adversaries may use steganographic techniques to hide command and control traffic to make detection efforts more difficult.
attack.mitre.org →
T1001.003 Protocol or Service Impersonation Command And Control
Adversaries may impersonate legitimate protocols or web service traffic to disguise command and control activity and thwart analysis efforts.
attack.mitre.org →
T1003.001 LSASS Memory Credential Access
Adversaries may attempt to access credential material stored in the process memory of the Local Security Authority Subsystem Service (LSASS).
attack.mitre.org →
T1003.003 NTDS Credential Access
Adversaries may attempt to access or create a copy of the Active Directory domain database in order to steal credential information, as well as obtain other information about domain members such as devices, users, and access rights.
attack.mitre.org →
T1003.005 Cached Domain Credentials Credential Access
Adversaries may attempt to access cached domain credentials used to allow authentication to occur in the event a domain controller is unavailable.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-1177Same vendor: Lfprojects
CVE-2024-27134Same vendor: Lfprojects
CVE-2025-67733Same vendor: Lfprojects
CVE-2024-27133Same vendor: Lfprojects
CVE-2024-27132Same vendor: Lfprojects
CVE-2026-27623Same vendor: Lfprojects
CVE-2023-6975Same vendor: Lfprojects
CVE-2023-2780Same vendor: Lfprojects
CVE-2023-6977Same vendor: Lfprojects
CVE-2023-1176Same vendor: Lfprojects

Affected Assets

lfprojects
case python utilities
0.10.0, 0.11.0, 0.12.0, 0.13.0, 0.14.0
lfprojects
cdo local uuid utility
0.4.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 3 hardening rules · 1 OS baseline
Validate
Prove the fix (OWASP ASVS)
  • V13.4.2
  • V6.5.3
  • V7.2.3
  • V11.5.1

Mitigating Controls (NIST 800-53 r5) AI

CM-7 Least Functionality good match

Least functionality directly prohibits enabling unnecessary debug features that would expose the inserted sensitive data.

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation will discover debug code containing sensitive information before release.

SC-12 Cryptographic Key Establishment and Management good match

Proper cryptographic key establishment and management includes using unpredictable seeds for PRNGs that feed key generation.

SA-15 Development Process, Standards, and Tools partial match

Requiring documented secure development processes and standards stops insertion of sensitive data into debug paths.

SA-8 Security and Privacy Engineering Principles partial match

Engineering principles can require cryptographically secure PRNGs seeded from high-entropy sources.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.DS-10 partial match
blocks

Explicitly calls for removing confidential data from processes, logs, and memory dumps that debug code commonly exposes.

PR.PS-01 partial match
blocks

Hardened configuration baselines and deployment checks can ensure debug features and associated data are disabled in production.

PR.PS-06 partial match
blocks

Secure SDLC practices directly prevent developers from embedding sensitive information inside debugging statements or code paths.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.19 Installation of software on operational systems partial match
removes
A.8.24 Use of cryptography partial match
blocks

A.8.24 requires proper use of cryptography (algorithms, key management, protection of information) but does not address or stop the use of a predictable PRNG seed; the weakness can still arise and be exploited in any cryptographic implementation that follows the clause.

A.8.25 Secure development life cycle partial match
blocks

Secure SDLC mandates removal of debug code and sensitive data before release.

A.8.26 Application security requirements partial match
removes
A.8.27 Secure system architecture and engineering principles partial match
blocks

Secure architecture principles include choosing cryptographically strong random number generation.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly prohibit embedding secrets or debug statements.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (higher-evidence rows only; rows rated `none` are excluded).

Oracle Linux 8 (3 rules)
  • V-248563 The OL 8 SSH server must be configured to use strong entropy. blocks CWE-337
  • V-248600 OL 8 must have the packages required to use the hardware random number generator entropy gatherer service. blocks CWE-337
  • V-248599 OL 8 must enable the hardware random number generator entropy gatherer service. blocks CWE-337

References