Security · 7 min read
Blast-RADIUS (CVE-2024-3596) Explained: Is Your Network Still Exposed?
Blast-RADIUS (CVE-2024-3596) lets attackers forge RADIUS Access-Accept responses. Learn what is affected, why EAP is safer, and the exact steps to mitigate: Message-Authenticator, server upgrades and RADIUS over TLS.
Blast-RADIUS (CVE-2024-3596) is a flaw in the RADIUS protocol itself. It lets an attacker who can intercept RADIUS traffic turn a rejected login into an accepted one. It affects nearly all RADIUS-over-UDP implementations that use PAP, CHAP or MS-CHAP. The fix is to require the Message-Authenticator attribute on every packet, upgrade RADIUS servers and clients, and move RADIUS that crosses untrusted networks into TLS.
What happened
Researchers disclosed Blast-RADIUS in July 2024 in the paper "RADIUS/UDP Considered Harmful" (USENIX Security 2024). RADIUS protects its responses with an MD5-based Response Authenticator. The attack uses an MD5 chosen-prefix collision, hidden inside a Proxy-State attribute, so that a forged Access-Accept carries a valid authenticator. The attacker does not learn the password or the shared secret; they simply get in. In the proof of concept the collision took minutes, but it can be computed faster with more resources.
Who is affected
| Use of RADIUS | Risk |
|---|---|
| PAP, CHAP or MS-CHAP over UDP across a WAN or the internet (VPN gateways, admin logins, some ISP and roaming setups) | High |
| The same, but inside one isolated management VLAN | Lower: the attacker must already be on that network |
| 802.1X / WPA2- and WPA3-Enterprise using EAP | Not practically exploitable, because EAP requires Message-Authenticator |
| RADIUS accounting only | Theoretical only |
| RADIUS over TLS (RadSec) or inside IPsec | Protected by the tunnel |
How to mitigate, in order
- Upgrade RADIUS servers first. Patched servers add Message-Authenticator to every response. FreeRADIUS fixed this in 3.0.27 and 3.2.5. Commercial NAC and policy servers released fixes in 2024.
- Require Message-Authenticator. Enable it on the server per client, and on each switch, AP, controller and VPN gateway once its firmware supports it.
- Upgrade the clients (NAS devices). Apply vendor firmware that sends and validates Message-Authenticator.
- Get RADIUS off untrusted networks. Carry it inside IPsec or a site-to-site VPN, or use RadSec (RADIUS over TLS, RFC 6614, TCP 2083).
- Prefer EAP-based methods such as EAP-TLS and PEAP over PAP and CHAP.
The step-by-step commands are in our RADIUS hardening tutorial.
What does not fix it
- Shorter RADIUS timeouts: collisions get faster with more computing power.
- MFA alone: the attacker forges the final accept, so the second factor can be bypassed when the second factor's result travels over the same vulnerable RADIUS exchange.
- Longer shared secrets: good practice, but irrelevant to this attack.
Is it still relevant in 2026?
Yes. The flaw is in the protocol, so any server or device that has not been upgraded and configured remains exposed. Older switches, VPN concentrators and firewalls that no longer get firmware are the usual gap. The IETF RADEXT working group is moving RADIUS toward TLS-only transport for this reason. Include RADIUS in your next vulnerability review and see the Navijin firmware page for current releases.
FAQ
Frequently asked questions
What is CVE-2024-3596?
The identifier for Blast-RADIUS, a protocol-level vulnerability that lets a man-in-the-middle forge RADIUS Access-Accept responses using an MD5 collision.
Is WPA2/WPA3-Enterprise Wi-Fi vulnerable to Blast-RADIUS?
Not in practice. 802.1X uses EAP, which already requires the Message-Authenticator attribute that blocks the attack.
How do I fix Blast-RADIUS?
Upgrade RADIUS servers and clients, require Message-Authenticator on all packets, and carry RADIUS over TLS or IPsec when it crosses untrusted networks.
Does Blast-RADIUS reveal passwords?
No. It forges an accept decision; it does not reveal user passwords or the RADIUS shared secret.
Related
Keep reading
Harden RADIUS step by step
Read more →RADIUS vs TACACS+
Read more →WPA3-Enterprise with RADIUS
Read more →What Is a SOC (Security Operations Center)? Roles, Tools and AI SOC Explained
What is a SOC? How a security operations center works, SOC analyst tiers, core tools (SIEM, EDR/XDR, SOAR), in-house vs managed SOC, what an AI SOC is, and how it differs from SOC 2 compliance.
Read more →What Is a RADIUS Server? How RADIUS Authentication Works
What is a RADIUS server and how does RADIUS authentication work? The Access-Request flow, ports 1812/1813, common uses for Wi-Fi, 802.1X and VPN, popular RADIUS servers and how to secure them.
Read more →VPN Terms Explained: VPN Tunnel, Concentrator, Passthrough, Kill Switch and VPN Router
Clear answers to common VPN questions: what a VPN tunnel is, what a VPN concentrator does, VPN passthrough, VPN kill switch, VPN routers, split tunnelling and site-to-site vs remote-access VPN.
Read more →Need help designing your network?
Navijin engineers provide free design consultations, bills of materials and quotations for business projects.