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.
The product does not validate or incorrectly validates the integrity check values or "checksums" of a message. This may prevent it from detecting if the data has been modified or corrupted in transmission.
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
Link | Tags |
---|---|
https://datatracker.ietf.org/doc/html/rfc2865 | technical description |
https://datatracker.ietf.org/doc/draft-ietf-radext-deprecating-radius/ | technical description |
https://networkradius.com/assets/pdf/radius_and_md5_collisions.pdf | third party advisory |
https://www.blastradius.fail/ | technical description |
http://www.openwall.com/lists/oss-security/2024/07/09/4 | mailing list |
https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2024-0014 | third party advisory |
https://security.netapp.com/advisory/ntap-20240822-0001/ | third party advisory |
https://today.ucsd.edu/story/computer-scientists-discover-vulnerabilities-in-a-popular-security-protocol | third party advisory |