mailing list archives
Re: CVE request: radsecproxy incorrect x.509 certificate validation
From: Raphael Geissert <geissert () debian org>
Date: Tue, 30 Oct 2012 13:46:21 -0600
On Wednesday 17 October 2012 12:48:19 Raphael Geissert wrote:
Ralf Paffrath discovered that radsecproxy may incorrectly accept a client
certificate if the certificates chain was validated with the CA settings
of one configuration block but the other certificate constraints failed,
and the certificate constraints of another configuration block passed
(ignoring this other config block's CA settings.)
This issue has been fixed in version 1.6.1. However, it introduces a
minor regression as it ignores some configuration blocks (see the
references for further details.)
While checking the issue I noticed that the same issue also affects
radsecproxy's DTLS support, which was not fixed. Upstream has now released
version 1.6.2 addressing the vulnerability in its DTLS support code.
Now, the thing is that upstream re-used the previously assigned CVE id
CVE-2012-4523. According to the guidelines a new id should be assigned since
they affect different versions even if the issues are related.
So, I guess a new id is in order?
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net