CVE-2024-57965
Axios ≤ 1.7.8
Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:N/A:NSummary
CVE-2024-57965 is a uncategorised-severity Origin Validation Error (CWE-346) vulnerability in Axios Axios. Its CVSS base score is 0.0.
Operationally, exploitation aligns with the MITRE ATT&CK technique DHCP Spoofing (T1557.003); ranked at the 31th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-4 (Information Flow Enforcement) and IA-3 (Device Identification and Authentication) — 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-57965 affects the Axios JavaScript library in versions prior to 1.7.8. The issue is located in the lib/helpers/isURLSameOrigin.js file, which fails to use a URL object when determining an origin and includes a potentially unwanted setAttribute('href', href) call.
The vulnerability carries a CVSS v3.1 base score of 0.0 (AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:N/A:N), indicating no impact on confidentiality, integrity, or availability. It is classified under CWE-346 (Origin Validation Error) and could theoretically be exploited by remote attackers with no privileges or user interaction, though it requires high attack complexity and results in a scope change with no measurable effects.
Mitigation is available via the Axios v1.7.8 release, which incorporates changes from GitHub pull request #6714, issue #6351, and commit 0a8d6e19da5b9899a2abafaaa06a75ee548597db. Notably, some parties contend that the fix only addresses a warning generated by a Static Application Security Testing (SAST) tool rather than resolving a genuine vulnerability.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-53865
Vulnerability Data
In axios before 1.7.8, lib/helpers/isURLSameOrigin.js does not use a URL object when determining an origin, and has a potentially unwanted setAttribute('href',href) call. NOTE: some parties feel that the code change only addresses a warning message from a SAST tool and…
more
does not fix a vulnerability.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 3 hardening rules · 1 OS baseline
—
Mitigating Controls (NIST 800-53 r5) AI
Information flow enforcement directly requires validating the source of data before allowing transmission or receipt.
Device identification and authentication mandates verifying the source before establishing connections.
Session authenticity mechanisms require validation that communications originate from the expected party.
Boundary protection at interfaces enforces checks on the origin of incoming communications.
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.
Authentication directly verifies the source of users/services/hardware, mitigating origin validation failures.
Verifying identity assertions enforces origin validation for conveyed claims.
Documenting authorized flows supports origin validation by defining expected sources.
Protecting networks from unauthorized access requires origin checks on communication sources.
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.
Network security controls enforce origin validation at network boundaries.
Security of network services includes validating the authenticity of service endpoints.
Network segregation reduces exposure but does not directly validate origins.
Application security requirements explicitly call for origin validation of inputs and communications.
Secure architecture principles encourage origin checks but do not mandate them.
Secure coding practices include implementing proper origin validation to prevent spoofing.
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` (authoritative rows only; rows rated `none` are excluded).
Oracle Linux 8 (3 rules)
- V-248574 YUM must be configured to prevent the installation of patches, service packs, device drivers, or OL 8 system components that have not been digitally signed using a certificate that is recognized and approved by the organization. prevents CWE-346
- V-248575 OL 8 must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. prevents CWE-346
- V-248827 OL 8 must not have the rsh-server package installed. prevents CWE-346