Multiple implementations of the RADIUS protocol do not adequately validate the vendor-length of the vendor-specific attributes

Overview Various RADIUS servers and clients permit the passing of vendor-specific and user-specific attributes. Several implementations of RADIUS fail to check the Vendor-Length of the Vendor-Specific attribute. It's possible to cause a denial of service against RADIUS servers with a malformed...

Multiple implementations of the RADIUS protocol contain a digest calculation buffer overflow

Overview Multiple implementations of the RADIUS protocol contain a buffer overflow in the function that calculates message digests. Description During the message digest calculation, a string containing the shared secret is concatenated with a packet received without checking the size of the targ...

RADIUS protocol and implementation weakness

There are few cryptographic problems allow to analize sniffed traffic. There is a possibility of request spoofing. Some implementation problems allow to DoS server or to elevate priveges...

An Analysis of the RADIUS Authentication Protocol

An Analysis of the RADIUS Authentication Protocol by Joshua Hill, InfoGard Laboratories www.infogard.com Last Modified Mon Nov 12 16:12:53 PST 2001 A current HTML version of this paper can be found at: http://www.untruth.org/josh/security/radius Please send comments to [email protected] 1...

More problems with RADIUS (protocol and implementations)

Hello bugtraq, There are more problems in RADIUS protocol and some of implementations: 1. There is no way RADIUS server can validate Access-Request packet really originated by NAS RADIUS client before and even after, if packet has no User-Password attribute decoding all attributes. It opens a...