First published: Tue Nov 20 2012(Updated: )
radsecproxy before 1.6.1 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.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Uninett Radsecproxy | <=1.6 | |
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 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.