Freeradius

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.

Published: 2024-07-09T12:02:53.001Z
Updated: 2026-06-09T09:01:52.617Z

A flaw was found in freeradius. A malicious RADIUS client or home server can send a malformed abinary attribute which can cause the server to crash.

Published: 2023-01-17T00:00:00.000Z
Updated: 2025-11-03T19:27:40.244Z

In freeradius, when an EAP-SIM supplicant sends an unknown SIM option, the server will try to look that option up in the internal dictionaries. This lookup will fail, but the SIM code will not check for that failure. Instead, it will dereference a NULL pointer, and cause the server to crash.

Published: 2023-01-17T00:00:00.000Z
Updated: 2025-11-03T19:27:38.875Z

In freeradius, the EAP-PWD function compute_password_element() leaks information about the password which allows an attacker to substantially reduce the size of an offline dictionary attack.

Published: 2023-01-17T00:00:00.000Z
Updated: 2025-11-03T19:27:37.502Z

In FreeRADIUS 3.0.x before 3.0.20, the EAP-pwd module used a global OpenSSL BN_CTX instance to handle all handshakes. This mean multiple threads use the same BN_CTX instance concurrently, resulting in crashes when concurrent EAP-pwd handshakes are initiated. This can be abused by an adversary as a Denial-of-Service (DoS) attack.

Published: 2020-03-21T00:13:05.000Z
Updated: 2024-08-05T01:33:17.262Z