CVE-2024-3502
Published: 14 November 2024
Summary
CVE-2024-3502 is a high-severity Insertion of Sensitive Information Into Sent Data (CWE-201) vulnerability in Lunary Lunary. Its CVSS base score is 8.1 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Unsecured Credentials (T1552); ranked at the 45.9th 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.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-32088
Vulnerability details
In lunary-ai/lunary versions up to and including 1.2.5, an information disclosure vulnerability exists where account recovery hashes of users are inadvertently exposed to unauthorized actors. This issue occurs when authenticated users inspect responses from `GET /v1/users/me` and `GET /v1/users/me/org` endpoints.…
more
The exposed account recovery hashes, while not directly related to user passwords, represent sensitive information that should not be accessible to unauthorized parties. Exposing these hashes could potentially facilitate account recovery attacks or other malicious activities. The vulnerability was addressed in version 1.2.6.
- 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.ai is an open-source LLM observability and management platform, fitting 'Other Platforms' as it provides infrastructure for monitoring and managing AI/LLM applications, and the vulnerability is in its API endpoints.
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
The vulnerability exposes account recovery hashes via API endpoints accessible to authenticated users, enabling adversaries to steal unsecured credentials.
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.
Embedding taints allows detection when sensitive data is inserted into outbound or sent data streams.
Storing information as fragments on distinct components is an architectural control that avoids insecure single-location storage of the complete sensitive data set.