Feature #15952
closed
Support Message-Authenticator in the PHP RADIUS client
100%
Description
In response to Blast-RADIUS (CVE-2024-3596), we need more secure options for User Authentication via RADIUS. Ideally, we'd have support for EAP protocol types rather than the insecure MS-CHAP and even more insecure PAP. Or at the least, support for using the Message-Authenticator attribute in the packet.
We already have support for EAP protocol types in FreeRADIUS and for authenticating IPSec, so I'm not sure why it's not part of the User authentication RADIUS client too.
Files
| RADIUSPRTCL.png (47.8 KB) RADIUSPRTCL.png | List of currently available protocols for RADIUS authentication client | ||
| clipboard-202511121020-gmo8v.png (88.2 KB) clipboard-202511121020-gmo8v.png |
Updated by Jim Pingle 11 months ago
- Status changed from New to Needs Patch
- Priority changed from High to Normal
We are limited by what is supported in the underlying upstream PHP RADIUS libraries, which lack such support. If an alternative presents itself, we can look into changing.
If communication with the RADIUS server only happens over secure, trusted links (e.g. VPN or secure network segments), such vulnerabilities are irrelevant.
Updated by Alex Kolesnik 3 months ago
Hi Jim. Looks like this radius client implementation supports the required attribute - https://codeberg.org/fkooman/php-radius
Updated by Christian McDonald 22 days ago
- Status changed from Needs Patch to In Progress
- Assignee set to Christian McDonald
- Target version set to CE-Next
- Plus Target Version set to 25.11
Updated by Christian McDonald 22 days ago
- Status changed from In Progress to Feedback
Updated by Marcos M 22 days ago
- Subject changed from User Auth RADIUS Client Secure Protocols to Support Message-Authenticator in the PHP RADIUS client
- Target version changed from CE-Next to 2.9.0
- % Done changed from 0 to 100
Tested working; "Require Message Authenticator" can now be set to "Yes" in FreeRADIUS when using pfSense as a client.
Updated by Ansley Barnes 21 days ago
Is there a chance that this could be extended to the L2TP RADIUS authentication section?