cbcvebase.
CVE-2024-3596
published 2024-07-09

CVE-2024-3596: 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…

PriorityP265critical9CVSS 3.1
AVNACHPRNUINSCCHIHAH
EPSS
14.86%
96.7th percentile
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.

Affected

23 ranges
VendorProductVersion rangeFixed in
debianfreeradius< freeradius 3.2.5+dfsg-1 (forky)freeradius 3.2.5+dfsg-1 (forky)
freeradiusfreeradius< 3.0.273.0.27
freeradiusfreeradius>= 0 < 3.2.5+dfsg-13.2.5+dfsg-1
freeradiusfreeradius>= 0 < 3.2.5+dfsg-13.2.5+dfsg-1
ietfrfc——
msrcwindows_10——
msrcwindows_10_version_1607——
msrcwindows_10_version_1809——
msrcwindows_10_version_21h2——
msrcwindows_10_version_22h2——
msrcwindows_11_version_21h2——
msrcwindows_11_version_22h2——
msrcwindows_11_version_23h2——
msrcwindows_server_2008——
msrcwindows_server_2008_r2——
msrcwindows_server_2012——
msrcwindows_server_2012_r2——
msrcwindows_server_2016——
msrcwindows_server_2019——
msrcwindows_server_2022——
paloaltocloud_ngfw——
paloaltopan-os——
paloaltoprisma_access——

Detection & IOCsextracted from sources · hover to see the quote

  • →Monitor for RADIUS traffic (UDP/1812 or UDP/1645) traversing non-management or non-dedicated VLANs — on-path interception of RADIUS responses is required for exploitation ↗
  • →Alert on RADIUS Access-Accept, Access-Reject, or Access-Challenge responses that have been modified in transit — the attack forges any valid response into another response type using an MD5 chosen-prefix collision against the Response Authenticator field ↗
  • →Track Cisco bug IDs CSCwq90178, CSCwk87884, CSCwk71992, CSCwk69454, CSCwk71817 for affected Cisco product patches related to this RADIUS spoofing vulnerability ↗
  • →Reference CERT/CC VU#456537 for additional technical indicators and researcher disclosures related to the Blast-RADIUS attack ↗
  • ·The attack requires an on-path (MitM) attacker capable of intercepting and modifying RADIUS UDP traffic between the NAS/client and the RADIUS server — purely passive or remote-only attackers cannot exploit this without network positioning ↗
  • ·Exploitation is only relevant when devices are configured to use remote RADIUS authentication — devices not using RADIUS are unaffected ↗
  • ·The vulnerability is rooted in the MD5-based Response Authenticator defined in RFC 2865; deployments using RADIUS over TLS (RadSec) or requiring Message-Authenticator in all packets are not exploitable via this vector ↗
  • ·No known public exploitation specifically targeting this vulnerability has been reported to CISA at the time of advisory publication ↗

CVSS provenance

nvdv3.19.0CRITICALCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
ghsa9.0CRITICAL
osv9.0CRITICAL
vendor_cisco9.0CRITICAL
vendor_debian9.0CRITICAL
vendor_oracle9.0CRITICAL
vendor_redhat9.0CRITICAL
vendor_msrc7.5HIGH
Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.