From: Francis Dupont <fdupont@isc.org>
Date: Mon, 26 Jan 2026 13:58:00 +0000 (+0100)
Subject: [#4254] Updated ARM
X-Git-Tag: Kea-3.1.5~5
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=de326792541824f70e4bbbc3f22ec50a54ffb85a;p=thirdparty%2Fkea.git

[#4254] Updated ARM
---

diff --git a/doc/sphinx/arm/ext-radius.rst b/doc/sphinx/arm/ext-radius.rst
index fbd514412a..4819bd6a1c 100644
--- a/doc/sphinx/arm/ext-radius.rst
+++ b/doc/sphinx/arm/ext-radius.rst
@@ -3,6 +3,33 @@
 RADIUS
 ======
 
+.. _radius-security-warning:
+
+Security Warning
+----------------
+
+RADIUS/UDP (and RADIUS/TCP) security is based on direct use of MD5
+with the shared secret and the access user password. These security
+mechanisms were known to be weak but things changed with the publication
+of the `Blast-RADIUS vulnerability <https://www.blastradius.fail>`__
+(`CVE-2024-3596 <https://www.cve.org/CVERecord?id=CVE-2024-3596>`__).
+
+To summary when the infrastructure between the RADIUS client
+(here the Kea DHCP server) and the RADIUS server is not protected
+a man-in-the-middle attacker can forge a valid accept message in
+response to a failed access / authentication request.
+
+Some RADIUS servers including the popular FreeRADIUS server already
+refuse by default to server requests which are considered as insecure
+because not protected using the Message-Authenticator attribute (based
+on HMAC-MD5 so not vulnerable and supported by Kea 3.1.5) so even when
+the infrastructure is protected RADIUS deployment is impacted by
+Blast-RADIUS.
+
+The planned (for Kea release 3.1.6) solution is to support
+RADIUS/TLS which provides  a built-in cryptographic protection
+of communications between RADIUS clients and servers.
+
 .. _radius-overview:
 
 RADIUS Overview
diff --git a/doc/sphinx/arm/security.rst b/doc/sphinx/arm/security.rst
index 1e8b4ef84c..7b3751f0f6 100644
--- a/doc/sphinx/arm/security.rst
+++ b/doc/sphinx/arm/security.rst
@@ -563,6 +563,12 @@ and DDNS servers since Kea version 2.7.2.
 The three primary Kea daemons (:iscman:`kea-dhcp4`, :iscman:`kea-dhcp6` and :iscman:`kea-dhcp-ddns`) all support a control
 channel, which is implemented as a UNIX socket. The control channel, which opens a UNIX socket, is disabled by default.
 
+Blast RADIUS
+------------
+
+Blast-RADIUS is a vulnerability that affects the RADIUS protocol implemented
+by the RADIUS hook library. See :ref:`radius-security-warning` for details.
+
 .. _sec-kea-runtime-security-policy-checking:
 
 Kea Runtime Security Policy Checking