Debian Fixes Two radsecproxy Denial-of-Service Vulnerabilities
Quick Answer
Update Debian trixie radsecproxy to 1.11.2-1+deb13u2. Review attribute rewriting and dynamic TLS-PSK lookup, then test RADIUS authentication, accounting and failover.
Confirm Scope And Apply The Supported Remediation
What to do now: Identify trixie RADIUS and RadSec proxies, package versions, upstream peers, client source restrictions, rewrite rules, dynamic lookup and TLS-PSK configuration. Check ModifyAttribute, ModifyVendorAttribute and SupplementVendorAttribute rules for the first issue. For the second, check dynamic server blocks using DynamicLookupCommand with PSKKey and PSKIdentity. Do not assume every RADIUS deployment is affected. Install 1.11.2-1+deb13u2 from the Debian trixie security repository. Upstream lists 1.11.5 as its fixed release; Debian provides a distribution backport, so an older upstream version string alone does not establish that the patched Debian package is vulnerable. Coordinate proxy restarts and verify authentication, accounting, trusted-peer TLS connections and failover. Retain installed-package output, approved configuration changes, service-start logs and representative end-to-end test results.
Last verified: 2026-11-16 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | Debian 13 trixie radsecproxy RADIUS and RadSec proxy |
|---|---|
| Advisory | DSA-6632-1 |
| CVEs | Not yet assigned in DSA-6632-1. |
| Authoritative release date | 2026-11-15 19:57:56 UTC — Debian security announcement message header. |
| Authority revision date | No separate material advisory revision is confirmed. |
| Affected versions | Debian trixie radsecproxy before 1.11.2-1+deb13u2. Review client attribute-rewrite rules and dynamic server lookup combined with TLS-PSK to establish applicability. |
| Fixed version | Debian trixie radsecproxy 1.11.2-1+deb13u2 |
| CVSS base score | Not provided by the authority |
| CVSS severity | Not provided by the authority |
| Exploitation status | Debian does not confirm exploitation in the wild in DSA-6632-1; no exploitation claim is inferred. |
What Changed
Debian issued DSA-6632-1 for two radsecproxy flaws that can stop the proxy and interrupt RADIUS authentication and accounting. The upstream reports concern malformed vendor attributes reaching rewrite rules and memory ownership during dynamic lookup with TLS-PSK. Debian states that CVE identifiers are not yet available.
What To Validate Now
- Inventory. Identify trixie RADIUS and RadSec proxies, package versions, upstream peers, client source restrictions, rewrite rules, dynamic lookup and TLS-PSK configuration.
- Establish applicability. Check ModifyAttribute, ModifyVendorAttribute and SupplementVendorAttribute rules for the first issue. For the second, check dynamic server blocks using DynamicLookupCommand with PSKKey and PSKIdentity. Do not assume every RADIUS deployment is affected.
- Remediate. Install 1.11.2-1+deb13u2 from the Debian trixie security repository. Upstream lists 1.11.5 as its fixed release; Debian provides a distribution backport, so an older upstream version string alone does not establish that the patched Debian package is vulnerable.
- Validate. Coordinate proxy restarts and verify authentication, accounting, trusted-peer TLS connections and failover. Retain installed-package output, approved configuration changes, service-start logs and representative end-to-end test results.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
Proxy failure can interrupt dependent network access. Upstream recommends trusted client source restrictions and RequireMessageAuthenticator for UDP/TCP as mitigations for the rewrite flaw. It gives no workaround for the dynamic TLS-PSK flaw and discourages that configuration. Debian supplies no CVSS score; this trixie package is not a claim of remediation for bookworm.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
- Debian DSA-6632-1 announcement
- Debian package security tracker
- Upstream rewrite-rule advisory
- Upstream dynamic TLS-PSK advisory
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.

