CVE-2021-32642: Missing input validation in dynamic discovery example scripts.
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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2021-32642?
CVE-2021-32642 has a high severity due to the potential for configuration injection via crafted DNS records.
How do I fix CVE-2021-32642?
To fix CVE-2021-32642, ensure you upgrade to radsecproxy versions greater than 1.9.0 or apply relevant patches from your distribution.
Which software is affected by CVE-2021-32642?
CVE-2021-32642 affects Uninett Radsecproxy versions before 1.9.0 and Fedora versions 33 and 34.
Can exploitation of CVE-2021-32642 lead to data breaches?
Yes, exploitation of CVE-2021-32642 could lead to unauthorized configuration changes, which may lead to data breaches.
What are the initial steps to mitigate CVE-2021-32642?
Initial mitigation steps for CVE-2021-32642 include limiting exposure by controlling access to DNS records and applying software updates immediately.