Cyber Resilience

CVE-2024-8765

Lunary ≤ 1.4.23

Public PoC
Published
20 March 2025
Modified
02 July 2025
Patch / advisory
View advisory
CVSS Score v3 7.3
Click a component to see what it means
Raw vectorCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
EPSS Score 0.0078 53th percentile
Risk Priority 57 floored blend · peak EPSS

Summary

CVE-2024-8765 is a high-severity Improper Resolution of Path Equivalence (CWE-41) vulnerability in Lunary Lunary. Its CVSS base score is 7.3 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Data from Local System (T1005); ranked in the top 47% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

This vulnerability is AI-related — categorised as LLM Application Platforms; in the Privacy and Disclosure risk domain.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and AC-3 (Access Enforcement) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

In lunary-ai/lunary, the privilege check mechanism is flawed in version git afc5df4. The system incorrectly identifies certain endpoints as public if the path contains '/auth/' anywhere within it. This allows unauthenticated attackers to access sensitive endpoints by including '/auth/' in…

more

the path. As a result, attackers can obtain and modify sensitive data and utilize other organizations' resources without proper authentication.

CWE(s)
CWE-41

AI Security AnalysisAI

AI Category
LLM Application Platforms
Risk Domain
Privacy and Disclosure
OWASP Top 10 for LLMs 2025
None mapped
Classification Reason
Matched keywords: ai, lunary

Related Threats

MITRE ATT&CK Enterprise Techniques

T1005 Data from Local System Collection
Adversaries may search local system sources, such as file systems, configuration files, local databases, virtual machine files, or process memory, to find files of interest and sensitive data prior to Exfiltration.
attack.mitre.org →
T1083 File and Directory Discovery Discovery
Adversaries may enumerate files and directories or may search in specific locations of a host or network share for certain information within a file system.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-5386Same product: Lunary Lunary
CVE-2024-11300Same product: Lunary Lunary
CVE-2024-1626Same product: Lunary Lunary
CVE-2024-11137Same product: Lunary Lunary
CVE-2024-1625Same product: Lunary Lunary
CVE-2024-7456Same product: Lunary Lunary
CVE-2024-6862Same product: Lunary Lunary
CVE-2024-7474Same product: Lunary Lunary
CVE-2024-7476Same product: Lunary Lunary
CVE-2024-4154Same product: Lunary Lunary

Affected Assets

lunary
lunary
≤ 1.4.23

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SI-10 Information Input Validation good match

Input validation of file paths directly rejects or normalizes the special-character manipulations that create equivalent names.

AC-3 Access Enforcement partial match

Proper enforcement of file access authorizations structurally blocks disclosure when equivalent paths are presented.

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.PS-06 mostly match
prevents

Secure SDLC practices directly prevent introduction of improper path-resolution logic in software.

PR.IR-01 partial match
prevents

Path-equivalence flaws enable unauthorized file access that network segmentation and logical access controls can partially block.

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.28 Secure coding mostly match
prevents

Secure coding standards directly require canonical path resolution and input sanitization to prevent equivalence attacks.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect path-equivalence flaws before release, partially fulfilling the control.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle includes path-handling requirements that reduce equivalence-based disclosure.

A.8.26 Application security requirements partial match
prevents

Application security requirements can mandate canonicalization and input validation to block path equivalence.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles call for safe file-system abstractions that mitigate path traversal risks.

A.8.3 Information access restriction none match
none

Information access restriction limits what files can be reached, indirectly reducing impact of path-equivalence exploits.

References