Hardening RADIUS against MD5 collision attacks (BlastRADIUS)

Welcome to the Purple Technical Briefing. I'm your host, a Senior Technical Content Strategist at Purple. Today, we're tackling a critical, time-sensitive issue for any organisation running enterprise-grade WiFi: a newly practical vulnerability in a 30-year-old protocol that could allow attackers to walk straight through your digital front door. We're talking about the RADIUS protocol and the MD5 collision attack known as Blast-RADIUS. For our audience of IT managers, network architects, and CTOs in hospitality, retail, and large public venues, this isn't just a theoretical problem. It's a direct threat to your network integrity, data security, and compliance posture. In the next ten minutes, we'll break down what the vulnerability is, how it works, and most importantly, provide a clear, actionable roadmap for mitigation. Whether you're responsible for a 200-room hotel, a national retail chain, or a 60,000-seat stadium, this briefing is directly relevant to decisions you need to make this quarter. Let's start with some context. RADIUS - Remote Authentication Dial-In User Service - was designed in 1991, during the era of dial-up internet. It's a client-server protocol that handles authentication, authorisation, and accounting for network access. When a staff member or device connects to your enterprise WiFi, the access point acts as a RADIUS client and sends an authentication request to a central RADIUS server. The server checks the credentials and responds with either an Access-Accept or an Access-Reject. This exchange has been the backbone of enterprise network security for over three decades. The problem is that RADIUS was designed before modern cryptographic standards existed. The protocol uses the MD5 hashing algorithm to provide a basic integrity check on server responses - a field called the Response Authenticator. MD5 was first shown to be cryptographically broken in 2004. Yet here we are in 2024, and RADIUS is still relying on it. The industry knew MD5 was weak. The protocol simply never got updated. Now let's get into the technical deep-dive. The Blast-RADIUS attack, formally assigned CVE-2024-3596, was disclosed in July 2024 by a team of researchers from Boston University, UC San Diego, CWI Amsterdam, and Microsoft Research. It combines a protocol-level vulnerability with an MD5 chosen-prefix collision attack - and critically, with significant speed improvements that make the attack practical in real time. Here's how it works. A man-in-the-middle attacker positions themselves on the network path between the RADIUS client - your access point - and the RADIUS server. When a user attempts to authenticate, the attacker intercepts the Access-Request packet. They inject a specially crafted malicious attribute into this request. This attribute is designed to cause a mathematical collision: a situation where two different inputs produce the same MD5 hash. The attacker pre-computes this collision so that the MD5 hash of the legitimate Access-Reject response from the server matches the MD5 hash of a forged Access-Accept response that the attacker has constructed. When the server returns its Access-Reject, the attacker substitutes their forged Access-Accept. The RADIUS client checks the Response Authenticator, finds it valid - because the MD5 hashes match - and grants network access. The attacker never needed to know the user's password. They never needed to know the shared secret between the RADIUS client and server. They simply exploited the mathematical weakness in MD5 to make a forged response look legitimate. And with modern hardware, the required MD5 collision can be computed in under five minutes. This is not a theoretical attack. It is operationally viable today. This vulnerability affects all RADIUS deployments using PAP - Password Authentication Protocol - CHAP, and MS-CHAP authentication modes over UDP. These are extremely common in enterprise environments, particularly in legacy deployments. The only authentication modes that are immune are those using EAP - the Extensible Authentication Protocol - because EAP establishes its own cryptographic tunnel that is independent of the MD5 Response Authenticator. Let me put the business risk in concrete terms. Consider a hotel chain. An attacker who gains unauthorised access to the corporate network can move laterally to reach the property management system, access guest records, reach point-of-sale terminals, and potentially exfiltrate payment card data. The average cost of a hospitality sector data breach exceeds three million pounds. Under GDPR, a breach involving guest personal data can trigger fines of up to four percent of global annual turnover. Under PCI DSS, a breach involving cardholder data can result in mandatory forensic investigations, card brand fines, and potential loss of payment processing privileges. The financial and reputational stakes are substantial. Now for implementation recommendations. How do you defend against this? The response has two layers: immediate hardening and long-term modernisation. The immediate action is to apply vendor patches for CVE-2024-3596. Every major RADIUS vendor - Cisco ISE, Microsoft NPS, FreeRADIUS, Juniper, Aruba, Ruckus - has released updates. Alongside patching, the critical configuration change is to enforce the Message-Authenticator attribute on all RADIUS clients and servers. This attribute, defined in RFC 2869, provides an HMAC-based integrity check over the entire RADIUS packet. Unlike the Response Authenticator, the HMAC construction is not vulnerable to the chosen-prefix collision attack. Configuring your infrastructure to require this attribute - and to reject any message that arrives without it - closes the immediate attack vector. For FreeRADIUS, this means setting require_message_authenticator equals yes in your clients configuration file. For Microsoft NPS, it's a policy setting in your Network Policy configuration. This is a low-disruption change that can typically be deployed within a maintenance window. However, the Message-Authenticator enforcement is a stop-gap, not a solution. The long-term strategic response is to migrate to EAP-based authentication. The gold standard is WPA3-Enterprise with EAP-TLS. EAP-TLS uses certificate-based mutual authentication - both the client device and the RADIUS server must present valid digital certificates from a trusted Certificate Authority. This eliminates the shared secret entirely, removes the dependency on MD5, and provides a level of security that is immune to the entire class of attacks that Blast-RADIUS represents. For environments where deploying a full PKI infrastructure is complex - particularly venues with high device turnover or bring-your-own-device policies - PEAP with MSCHAPv2 is an acceptable interim step, provided that clients are configured to validate the RADIUS server certificate. Without server certificate validation, PEAP is vulnerable to rogue access point attacks, which is a separate but equally serious risk. The final phase of the modernisation roadmap is to deploy RADIUS over TLS, known as RADSEC. RADSEC encapsulates all RADIUS traffic within a mutually authenticated TLS session, providing full confidentiality and integrity for the entire authentication exchange. This makes transport-layer attacks like Blast-RADIUS impossible, because there is no unencrypted RADIUS traffic to intercept. RADSEC is particularly valuable in distributed environments - hotel chains, retail networks, stadium complexes - where RADIUS traffic may traverse multiple network segments between the access point and the central authentication server. Let's move to a rapid-fire Q&A. Question one: We use EAP. Are we safe? If you are using EAP-TLS, PEAP, or EAP-TTLS, you are not vulnerable to the specific Blast-RADIUS MD5 collision attack. However, you should still apply vendor patches as a defence-in-depth measure, and you should audit your configuration to ensure server certificate validation is enforced on all clients. Question two: Our RADIUS traffic is in a dedicated management VLAN. Does that protect us? It reduces the attack surface, but it does not eliminate the vulnerability. An attacker who has already compromised any device on the management network can still execute a man-in-the-middle attack. Segmentation is a valuable layer of defence, but it must be combined with Message-Authenticator enforcement and EAP migration. Question three: How difficult is the immediate mitigation? For most environments, enforcing the Message-Authenticator is a straightforward configuration change. The primary challenge is ensuring that all network devices - access points, switches, controllers - support the attribute and have it enabled. A device audit before enforcing the requirement server-side is essential to avoid authentication failures on legacy hardware. Question four: Can I detect whether I've been attacked? This is very difficult. The forged Access-Accept packet appears valid to the RADIUS client because the MD5 hash checks out. Your best detection approach is to monitor RADIUS accounting logs for anomalous successful authentications - unexpected device types, MAC addresses that don't match your inventory, or successful logins at unusual times. Integrate your RADIUS accounting data with your SIEM for automated alerting. To summarise and outline your next steps. The Blast-RADIUS vulnerability is a serious, practically exploitable threat to any organisation running legacy RADIUS authentication over UDP. The attack requires no credential knowledge and can be executed in minutes. Your immediate priority is to audit your infrastructure, apply vendor patches, and enforce the Message-Authenticator attribute on all RADIUS clients and servers. Your medium-term goal is to migrate to EAP-TLS and WPA3-Enterprise. Your long-term architectural target is RADSEC. At Purple, we provide the intelligence layer that helps you understand and secure your venue's WiFi network. Our platform gives you the visibility to identify device types, monitor authentication patterns, and ensure your security policies are being effectively enforced across every access point in your estate. Your action plan is three words: Audit, Patch, and Modernise. Don't let a 30-year-old protocol be the weak link in your security posture. Thank you for joining this Purple Technical Briefing. Stay secure.