CVE-2012-4566: Medium severity uninett radsecproxy vulnerability
Published Nov 20, 2012
·Updated
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.
Affected Software
18 affected components
Uninett Radsecproxy<=1.6.1
Uninett Radsecproxy=1.0
Uninett Radsecproxy=1.0-alpha
Uninett Radsecproxy=1.0-alpha-p1
Uninett Radsecproxy=1.0-p1
Uninett Radsecproxy=1.1
Uninett Radsecproxy=1.1-alpha
Uninett Radsecproxy=1.1-beta
Uninett Radsecproxy=1.2
Uninett Radsecproxy=1.3-alpha
Uninett Radsecproxy=1.3-beta
Uninett Radsecproxy=1.3.1
Uninett Radsecproxy=1.4
Uninett Radsecproxy=1.4.1
Uninett Radsecproxy=1.4.2
Uninett Radsecproxy=1.4.3
Uninett Radsecproxy=1.5
Uninett Radsecproxy=1.6
Event History
Nov 20, 2012
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
Description
Frequently Asked Questions
1
What is the severity of CVE-2012-4566?
CVE-2012-4566 is categorized as a medium severity vulnerability.
2
How do I fix CVE-2012-4566?
To fix CVE-2012-4566, upgrade radsecproxy to version 1.6.2 or later.
3
What systems are affected by CVE-2012-4566?
CVE-2012-4566 affects radsecproxy versions up to 1.6.1 and specific earlier versions.
4
What type of vulnerability is CVE-2012-4566?
CVE-2012-4566 is a security vulnerability related to improper certificate verification.
5
Can CVE-2012-4566 allow unauthorized access?
Yes, CVE-2012-4566 can potentially allow remote attackers to bypass access restrictions.