dbcve.org
FedoraOperating system · Fedoraproject

CVE-2021-32642

CRITICAL · 9.4 CVSS v3.1 Published 2021-05-28
Fix available
A fix is available. Upgrade to 1.9.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
radsecproxy is a generic RADIUS proxy that supports both UDP and TLS (RadSec) RADIUS transports. Missing input validation in radsecproxy's `naptr-eduroam.sh` and `radsec-dynsrv.sh` scripts can lead to configuration injection via crafted radsec peer discovery DNS records. Users are subject to Information disclosure, Denial of Service, Redirection of Radius connection to a non-authenticated server leading to non-authenticated network access. Updated example scripts are available in the master branch and 1.9 release. Note that the scripts are not part of the installation package and are not updated automatically. If you are using the examples, you have to update them manually. The dyndisc scripts work independently of the radsecproxy code. The updated scripts can be used with any version of radsecproxy.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

radsecproxy contains example discovery scripts (naptr-eduroam.sh and radsec-dynsrv.sh) that parse DNS NAPTR records for RadSec peer discovery without validating the parsed values, allowing attackers to inject configuration parameters via specially crafted DNS records. This enables information disclosure, DoS, and redirection of RADIUS connections to attacker-controlled servers.

MitigationUpdate the example scripts (naptr-eduroam.sh and radsec-dynsrv.sh) to the fixed versions from the radsecproxy master branch or 1.9 release, as these scripts are not included in the installation package and require manual updating.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FedoraOperating system
Affected:= 33= 34
RadsecproxyApplication
Affected:< 1.9.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check radsecproxy installation and version
    Query the installed package version (e.g., rpm -q radsecproxy, dpkg -l radsecproxy, or radsecproxy -v)
    Affected if Version is less than 1.9.0 on Fedora 33/34 or any version < 1.9.0 of Uninett radsecproxy
  2. Locate the example discovery scripts
    Search for naptr-eduroam.sh and radsec-dynsrv.sh in common locations such as /usr/share/doc/, /usr/local/share/, or the original source tree
    Affected if These scripts are present on the system
  3. Verify if dynamic peer discovery is enabled
    Examine the radsecproxy configuration file for 'dynsrv' or 'naptr' directives, or lines that invoke the example scripts
    Affected if Configuration references dynamic peer discovery using NAPTR records
  4. Check if scripts are actively referenced in runtime configuration
    Inspect config for 'exec' or 'dynamicServer' directives pointing to naptr-eduroam.sh or radsec-dynsrv.sh
    Affected if The scripts are executed by the configuration for peer discovery

A user is affected if radsecproxy version is below 1.9.0 AND the example discovery scripts (naptr-eduroam.sh or radsec-dynsrv.sh) are deployed and actively used for NAPTR-based dynamic peer discovery.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.9.0 or later
Fixed in 1.9.0
Interim mitigation

Update the example scripts (naptr-eduroam.sh and radsec-dynsrv.sh) to the fixed versions from the radsecproxy master branch or 1.9 release, as these scripts are not included in the installation package and require manual updating.

Recommended fix High confidence

radsecproxy 1.9.0 (or updated example scripts from master/1.9 branch)

  1. 1. Identify if you are using the vulnerable scripts: naptr-eduroam.sh or radsec-dynsrv.sh from radsecproxy examples
  2. 2. Locate the directory containing these example scripts in your deployment
  3. 3. Download the updated versions of naptr-eduroam.sh and radsec-dynsrv.sh from the radsecproxy master branch or 1.9 release (available at github.com/radsecproxy/radsecproxy)
  4. 4. Replace the existing vulnerable script files with the updated versions
  5. 5. Verify the new scripts have proper input validation by reviewing the code changes
  6. 6. Restart any radsecproxy or discovery services using these scripts
Caveat The example scripts are not part of the installation package and must be updated manually; this is a patch/mitigation rather than a version upgrade of radsecproxy itself

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fedora Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-32642 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-32642 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data