The DTLS support in radsecproxy before 1.6.2 does not properly verify certificates when…
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- — Not recorded in CVSS 2.0
- Attack complexity
- Low
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- Partial · Partial · None
- Fix status
- No fix listed
Attack profile from CVSS 2.0 · NVD. Fix status from CNA. Impact type from CWE-264.
Summary
The DTLS support in radsecproxy before 1.6.2 does not properly verify certificates when there are configuration blocks with CA settings that are unrelated to the block being used for verifying the certificate chain, which might allow remote attackers to bypass intended access restrictions and spoof clients, a different vulnerability than CVE-2012-4523.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | — | all versions | — | No fix listed | CNA |
- — Vendor— Affected all versions Fixed in — No fix listed CNA
CPE configurations NVD · 18
| CPE | Versions | Role | Vendor |
|---|---|---|---|
| cpe:2.3:a:uninett:radsecproxy:*:*:*:*:*:*:*:* | up to 1.6.1 | Vulnerable | uninett |
| cpe:2.3:a:uninett:radsecproxy:1.0:*:*:*:*:*:*:* | 1.0 | Vulnerable | uninett |
| cpe:2.3:a:uninett:radsecproxy:1.0:alpha:*:*:*:*:*:* | 1.0 alpha | Vulnerable | uninett |
| cpe:2.3:a:uninett:radsecproxy:1.0:alpha-p1:*:*:*:*:*:* | 1.0 alpha-p1 | Vulnerable | uninett |
| cpe:2.3:a:uninett:radsecproxy:1.0:p1:*:*:*:*:*:* | 1.0 p1 | Vulnerable | uninett |
| cpe:2.3:a:uninett:radsecproxy:1.1:*:*:*:*:*:*:* | 1.1 | Vulnerable | uninett |
| cpe:2.3:a:uninett:radsecproxy:1.1:alpha:*:*:*:*:*:* | 1.1 alpha | Vulnerable | uninett |
| cpe:2.3:a:uninett:radsecproxy:1.1:beta:*:*:*:*:*:* | 1.1 beta | Vulnerable | uninett |
| cpe:2.3:a:uninett:radsecproxy:1.2:*:*:*:*:*:*:* | 1.2 | Vulnerable | uninett |
| cpe:2.3:a:uninett:radsecproxy:1.3:alpha:*:*:*:*:*:* | 1.3 alpha | Vulnerable | uninett |
- cpe:2.3:a:uninett:radsecproxy:*:*:*:*:*:*:*:* Versions up to 1.6.1 Vulnerable ·uninett
- cpe:2.3:a:uninett:radsecproxy:1.0:*:*:*:*:*:*:* Versions 1.0 Vulnerable ·uninett
- cpe:2.3:a:uninett:radsecproxy:1.0:alpha:*:*:*:*:*:* Versions 1.0 alpha Vulnerable ·uninett
- cpe:2.3:a:uninett:radsecproxy:1.0:alpha-p1:*:*:*:*:*:* Versions 1.0 alpha-p1 Vulnerable ·uninett
- cpe:2.3:a:uninett:radsecproxy:1.0:p1:*:*:*:*:*:* Versions 1.0 p1 Vulnerable ·uninett
- cpe:2.3:a:uninett:radsecproxy:1.1:*:*:*:*:*:*:* Versions 1.1 Vulnerable ·uninett
- cpe:2.3:a:uninett:radsecproxy:1.1:alpha:*:*:*:*:*:* Versions 1.1 alpha Vulnerable ·uninett
- cpe:2.3:a:uninett:radsecproxy:1.1:beta:*:*:*:*:*:* Versions 1.1 beta Vulnerable ·uninett
- cpe:2.3:a:uninett:radsecproxy:1.2:*:*:*:*:*:*:* Versions 1.2 Vulnerable ·uninett
- cpe:2.3:a:uninett:radsecproxy:1.3:alpha:*:*:*:*:*:* Versions 1.3 alpha Vulnerable ·uninett
Show 8 more CPE
| CPE | Versions | Role | Vendor |
|---|---|---|---|
| cpe:2.3:a:uninett:radsecproxy:1.3:beta:*:*:*:*:*:* | 1.3 beta | Vulnerable | uninett |
| cpe:2.3:a:uninett:radsecproxy:1.3.1:*:*:*:*:*:*:* | 1.3.1 | Vulnerable | uninett |
| cpe:2.3:a:uninett:radsecproxy:1.4:*:*:*:*:*:*:* | 1.4 | Vulnerable | uninett |
| cpe:2.3:a:uninett:radsecproxy:1.4.1:*:*:*:*:*:*:* | 1.4.1 | Vulnerable | uninett |
| cpe:2.3:a:uninett:radsecproxy:1.4.2:*:*:*:*:*:*:* | 1.4.2 | Vulnerable | uninett |
| cpe:2.3:a:uninett:radsecproxy:1.4.3:*:*:*:*:*:*:* | 1.4.3 | Vulnerable | uninett |
| cpe:2.3:a:uninett:radsecproxy:1.5:*:*:*:*:*:*:* | 1.5 | Vulnerable | uninett |
| cpe:2.3:a:uninett:radsecproxy:1.6:*:*:*:*:*:*:* | 1.6 | Vulnerable | uninett |
- cpe:2.3:a:uninett:radsecproxy:1.3:beta:*:*:*:*:*:* Versions 1.3 beta Vulnerable ·uninett
- cpe:2.3:a:uninett:radsecproxy:1.3.1:*:*:*:*:*:*:* Versions 1.3.1 Vulnerable ·uninett
- cpe:2.3:a:uninett:radsecproxy:1.4:*:*:*:*:*:*:* Versions 1.4 Vulnerable ·uninett
- cpe:2.3:a:uninett:radsecproxy:1.4.1:*:*:*:*:*:*:* Versions 1.4.1 Vulnerable ·uninett
- cpe:2.3:a:uninett:radsecproxy:1.4.2:*:*:*:*:*:*:* Versions 1.4.2 Vulnerable ·uninett
- cpe:2.3:a:uninett:radsecproxy:1.4.3:*:*:*:*:*:*:* Versions 1.4.3 Vulnerable ·uninett
- cpe:2.3:a:uninett:radsecproxy:1.5:*:*:*:*:*:*:* Versions 1.5 Vulnerable ·uninett
- cpe:2.3:a:uninett:radsecproxy:1.6:*:*:*:*:*:*:* Versions 1.6 Vulnerable ·uninett
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2012-4566
- 2026-10-03 Alias added: GHSA-3qgg-3fwc-j9gv
References
Advisory 1
Other 5
- [radsecproxy] 20121025 Radsecproxy 1.6.1 is out
- [oss-security] 20121031 Re: Re: CVE request: radsecproxy incorrect x.509 certificate validation
- [radsecproxy] 20120913 Radsecproxy is mixing up pre- and post-TLS-handshake client verification
- [oss-security] 20121017 CVE request: radsecproxy incorrect x.509 certificate validation
- http://git.nordu.net/?p=radsecproxy.git%3Ba=commit%3Bh=3682c935facf5ccd7fa600644bbb76957155c680
More uninett Radsecproxy vulnerabilities
- TI-2021-12310 Missing input validation in dynamic discovery example scripts. CVSS 3.1CRITICAL 9.4
- TI-2012-03863 radsecproxy before 1.6.1 does not properly verify certificates when there are… CVSS 2.0MEDIUM 6.4
Sources
- CVE-2012-4566 · CVE Program
- CVE-2012-4566 · NVD
- FIRST EPSS
- GHSA-3qgg-3fwc-j9gv · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences