CVE-2024-3596
Freeradius ≤ 3.0.27
Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:HSummary
CVE-2024-3596 is a critical-severity Improper Validation of Integrity Check Value (CWE-354) vulnerability in Freeradius Freeradius. Its CVSS base score is 9.0 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Supply Chain Compromise (T1195); ranked in the top 4% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SC-13 (Cryptographic Protection) and SC-8 (Transmission Confidentiality and Integrity) — 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.
The vulnerability affects the RADIUS protocol as defined in RFC 2865, where the MD5-based Response Authenticator signature is susceptible to chosen-prefix collision attacks. This allows forgery of any valid response packet, including Access-Accept, Access-Reject, or Access-Challenge messages, without knowledge of the shared secret.
An attacker positioned to observe or intercept RADIUS traffic can exploit the issue to alter response contents, potentially granting unauthorized access, denying service, or manipulating authentication flows. The CVSS 9.0 score reflects network attack vector, high complexity, and impacts across confidentiality, integrity, and availability in a scoped environment.
Published references include an IETF draft on deprecating RADIUS, Siemens product security advisories, and the original RFC 2865 specification, pointing practitioners toward protocol migration and updated implementations. The associated EPSS score reached a peak of 0.2432 with a current value of 0.2216, indicating measurable post-disclosure interest that warrants monitoring.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-32175
Vulnerability Data
RADIUS Protocol under RFC 2865 is susceptible to forgery attacks by a local attacker who can modify any valid Response (Access-Accept, Access-Reject, or Access-Challenge) to any other response using a chosen-prefix collision attack against MD5 Response Authenticator signature.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 16 hardening rules · 4 OS baselines
V10.4.12
Mitigating Controls (NIST 800-53 r5) AI
Requires protection of integrity for transmitted information, directly stopping the failure to verify messages were unmodified in transit.
Requires integrity verification tools that detect unauthorized changes when checksum validation is missing or flawed.
Mandates cryptographic mechanisms that include integrity protection, preventing improper checksum validation.
Associates integrity-related security attributes with exchanged information, helping ensure modification can be detected during transmission.
Protects session authenticity, which structurally reduces the ability to undetectably modify messages in the channel.
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.
Directly requires integrity protection (e.g., signatures/hashes) for data-in-transit, which prevents the described weakness while also addressing confidentiality/availability.
Requires cryptographic hashes and signatures that directly enforce integrity-check validation for data at rest.
Mandates pre-acquisition integrity assessment, addressing only the initial portion of the weakness lifecycle.
Requires verification of backup integrity, covering validation only within recovery scenarios.
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.
Mandates network security controls that can enforce message integrity on channels.
Addresses security of network services, which may include integrity mechanisms.
Cryptographic controls mandate integrity mechanisms whose correct validation directly prevents CWE-354.
Secure coding standards require proper implementation and validation of checksums or MACs.
Security testing can detect missing integrity validation but does not itself implement the control.
Requires secure information transfer procedures that can include integrity checks.
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 (5 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-354, CWE-924
- 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-354
- V-248823 OL 8 must not have the telnet-server package installed. prevents CWE-924
Oracle Linux 9 (1 rule)
- V-271523 OL 9 must check the GPG signature of locally installed software packages before installation. prevents CWE-354
RHEL 7 (2 rules)
- V-204447 The Red Hat Enterprise Linux operating system must prevent the installation of software, patches, service packs, device drivers, or operating system components from a repository 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-354
- V-204448 The Red Hat Enterprise Linux operating system 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-354
RHEL 8 (2 rules)
- V-230264 RHEL 8 must prevent the installation of software, patches, service packs, device drivers, or operating system components from a repository 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-354
- V-230265 RHEL 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-354