The team did a successful attack in practice in January but had not yet made it public. Since then, they have been working with vendors on more secure solutions. They named the vulnerability ‘Blast-RADIUS’. The team will officially present their results at the international 33rd USENIX-Security Symposium, which takes place from 14-16 August in Philadelphia, USA.
Wi-Fi and VPN networks
RADIUS (Remote Authentication Dial-In User Service) was designed back in 1991 - in the era of dial-up Internet access - but it is still an important authentication protocol. It is used to access Wi-Fi and VPN networks, as well as routers, switches and other network equipment. RADIUS network traffic is typically transported unsecured via the so-called UDP network layer, protected only by cryptography based on the outdated MD5 standard. Despite the fact that MD5 has been shown to be unsafe since 2004, the RADIUS/UDP standard has hardly changed since then.
Very fast attack on MD5
There is a short login timeout of at most minutes, after which the login attempt will be aborted. Until now, so-called chosen-prefix attacks took about a day to break MD5 security. The researchers now present an improved, very fast attack on MD5 that just takes a few minutes and they show how it can force unauthorized access via RADIUS/UDP. This was partly possible thanks to improvements made by Stevens in his existing 'Hashclash' tool.
Migrate to RADIUS/TLS
Marc Stevens says: “The use of MD5 has been discouraged for a long time. Unfortunately, all too often, people wait until a concrete attack is demonstrated. Some dangerous examples from the past include a forged Certificate Authority (RogueCA, 2008, aka the “https crack”), a forged Windows Update (FLAME, 2012), a TLS attack (SLOTH, 2016), and bypassing Certificate Verification in Windows (2023). And now RADIUS, too.
The RADIUS/UDP standard has long failed to meet modern cryptographic standards. We therefore recommend the use of RADIUS/TLS, as TLS can provide strong privacy and security guarantees. RADIUS/TLS fits within zero-trust architectures — the strategic security model where no internal network is designated as trusted. Vendors and network administrators should change this.”