Critical · published July 9, 2024
🔥 A local attacker could exploit the RADIUS protocol with a chosen-prefix collision attack, turning any Access-Accept or Access-Reject into their call to action! Think of it like a magician swapping your concert ticket with a fake one right before you get inside — the show must go on for them, but it leaves you out in the cold! 🎩✨ The consequences can be absolutely devastating! An attacker could manipulate authentication responses, allowing unauthorized access to sensitive resources, essentially granting themselves VIP access where they don’t belong. This could compromise the integrity of the entire system and put valuable data at risk! ⚡
Think of it like a magician swapping your concert ticket with a fake one right before you get inside — the show must go on for them, but it leaves you out in the cold! 🎩✨ This vulnerability allows local attackers to modify RADIUS responses using a chosen-prefix collision against the MD5 Response Authenticator signature, resulting in forged authentication messages that can bypass legitimate access controls.
The consequences can be absolutely devastating! An attacker could manipulate authentication responses, allowing unauthorized access to sensitive resources, essentially granting themselves VIP access where they don’t belong. This could compromise the integrity of the entire system and put valuable data at risk! ⚡ To protect against this vulnerability, immediately update your RADIUS implementation to the latest version that addresses this forgery risk. Additionally, consider transitioning to a more secure hashing algorithm than MD5, if feasible, to bolster your defenses. 🛡️ You've got this! By taking these steps, you're on your way to fortifying your defenses and keeping your systems safe! 💪🚀
| Product | Versions | Fixed in |
|---|---|---|
| freeradius/freeradius | < 3.0.27 | 3.0.27 |
| broadcom/brocade_sannav | all versions | — |
| broadcom/fabric_operating_system | all versions | — |
| sonicwall/sonicos | all versions | — |