Project

General

Profile

Actions

Feature #15952

closed

Support Message-Authenticator in the PHP RADIUS client

Added by Matthew Ross 12 months ago. Updated 5 days ago.

Status:
Resolved
Priority:
Normal
Category:
Authentication
Target version:
Start date:
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
26.03
Release Notes:
Default

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 Matthew Ross, 12/24/2024 04:14 PM
clipboard-202511121020-gmo8v.png (88.2 KB) clipboard-202511121020-gmo8v.png Ansley Barnes, 11/12/2025 03:20 PM
clipboard-202512131136-oilga.png (8.31 KB) clipboard-202512131136-oilga.png Stefano Ceccherini, 12/13/2025 10:36 AM
Actions #1

Updated by Jim Pingle 12 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.

Actions #2

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

Actions #3

Updated by Christian McDonald about 1 month 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
Actions #5

Updated by Marcos M about 1 month 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.

Actions #6

Updated by Ansley Barnes about 1 month ago

Is there a chance that this could be extended to the L2TP RADIUS authentication section?

Actions #7

Updated by Marcos M about 1 month ago

  • Status changed from Feedback to Resolved

Not likely - best to try moving away from L2TP.

Actions #8

Updated by Stefano Ceccherini 7 days ago

Does this mean pfSense always sends the Message-Authenticator attributes now, or am I getting it wrong ?
Authentication does not work against Microsoft NPS if I check the box "Access-Request must contain the Message-Authenticator attribute"
The event log says the request does not contain the attribute.
If I clear the box, everything works correctly.

Actions #9

Updated by Marcos M 5 days ago

  • Plus Target Version changed from 25.11 to 26.03

My tests were from some Access Points and from Diagnostics > Authentication on pfSense 26.03. The Message-Authenticator attribute can be seen with a pcap. The change was picked to 25.11 but there must be something else missing there because I can't get it to work on 25.11.

Actions

Also available in: Atom PDF