CVE-2024-3501
Published: 14 November 2024
Summary
CVE-2024-3501 is a high-severity Insecure Storage of Sensitive Information (CWE-922) vulnerability in Lunary Lunary. Its CVSS base score is 8.1 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 45.1th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
This vulnerability is AI-related — categorised as Other Platforms; in the Privacy and Disclosure risk domain; MITRE ATLAS techniques in scope: User Execution (AML.T0011), AI Model Inference API Access (AML.T0040).
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-32087
Vulnerability details
In lunary-ai/lunary versions up to and including 1.2.5, an information disclosure vulnerability exists due to the inclusion of single-use tokens in the responses of `GET /v1/users/me` and `GET /v1/users/me/org` API endpoints. These tokens, intended for sensitive operations such as password…
more
resets or account verification, are exposed to unauthorized actors, potentially allowing them to perform actions on behalf of the user. This issue was addressed in version 1.2.6, where the exposure of single-use tokens in user-facing queries was mitigated.
- CWE(s)
AI Security AnalysisAI
- AI Category
- Other Platforms
- Risk Domain
- Privacy and Disclosure
- OWASP Top 10 for LLMs 2025
- None mapped
- Classification Reason
- Lunary is an open-source LLM engineering and observability platform (lunary-ai/lunary), fitting under 'Other Platforms' as an AI/ML operations tool, not specifically a framework, library, or assistant.
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
Vulnerability exposes single-use tokens for password resets/account verification via public-facing API endpoints, enabling exploitation of public-facing application (T1190), exploitation for credential access (T1212), and use of valid cloud accounts (T1078.004).
MITRE ATLAS TechniquesAI
MITRE ATLAS techniques
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Tracking information locations and access supports secure storage practices instead of insecure ones.
Establishing an alternate site with equivalent protections directly mitigates insecure storage of sensitive backup information.
Requiring protection of backup information directly addresses insecure storage of sensitive data in backups.
Policy explicitly addresses insecure storage of CUI on external systems, requiring compliant handling and protections.
Proper categorization drives selection of storage controls that keep sensitive information from being stored insecurely.
The control explicitly requires secure storage mechanisms for sensitive information, closing the insecure-storage weakness class.
Storing information as fragments on distinct components is an architectural control that avoids insecure single-location storage of the complete sensitive data set.
OPSEC requirements improve handling and storage practices for sensitive supply-chain information.