CVE-2024-43441
Apache Hugegraph 1.0.0 – 1.5.0
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2024-43441 is a critical-severity Authentication Bypass by Assumed-Immutable Data (CWE-302) vulnerability in Apache Hugegraph. Its CVSS base score is 9.8 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 0.7% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to IA-2 (Identification and Authentication (Organizational Users)) and AC-3 (Access Enforcement) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2024-43441 is an authentication bypass vulnerability classified under CWE-302 (Authentication Bypass by Assumed-Immutable Data) that affects Apache HugeGraph-Server versions 1.0.0 through 1.4.x. The flaw resides in the server's handling of data presumed to be immutable during authentication checks, allowing unauthorized access without valid credentials. It carries a CVSS 3.1 base score of 9.8, reflecting network-accessible exploitation with no required privileges or user interaction and full impact on confidentiality, integrity, and availability.
An unauthenticated remote attacker can exploit the issue over the network to bypass authentication controls entirely, potentially gaining the ability to read, modify, or delete data and perform administrative actions within the graph database server. Because the vulnerability requires no authentication or special conditions, it can be triggered through crafted requests that manipulate the assumed-immutable data structures used for identity verification.
Apache has published mitigation guidance recommending immediate upgrade to HugeGraph-Server 1.5.0, which contains the fix; the project advisory and the oss-security mailing list posting both direct users to this patched release and note that earlier versions remain exposed.
The CVE's EPSS score currently stands at 0.8944 with a recorded peak of 0.9042, indicating sustained high exploitation interest since disclosure.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-3580
Vulnerability Data
Authentication Bypass by Assumed-Immutable Data vulnerability in Apache HugeGraph-Server. This issue affects Apache HugeGraph-Server: from 1.0.0 before 1.5.0. Users are recommended to upgrade to version 1.5.0, which fixes the issue.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V7.2.4
Mitigating Controls (NIST 800-53 r5) AI
Mandates proper unique identification and authentication of users, precluding reliance on attacker-controlled immutable assumptions.
Requires server-side enforcement of authorizations instead of trusting client-supplied mutable data for authentication decisions.
Mandates proper identification and authentication for non-organizational users, precluding reliance on attacker-controlled immutable assumptions.
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.
Strong authentication mechanisms directly avoid reliance on attacker-controlled immutable data.
Protecting and verifying identity assertions prevents tampering with data assumed immutable during auth.
Least-privilege authorization policies reduce impact of bypassed authentication but do not address the root flaw.
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.
Security testing can discover and block authentication bypasses that rely on mutable data.
Access-control policy can mandate validation of all identity data, reducing reliance on assumed-immutable fields.
Identity-management processes can require verification of mutable attributes, mitigating the root cause.
Proper management of authentication information prevents use of client-controlled tokens or cookies as sole proof of identity.
Access-rights reviews can detect and revoke rights granted via tampered immutable data.
Secure SDLC practices include threat modeling and input-validation requirements that catch assumed-immutable data flaws.