[36075] in bugtraq
Re: Windows doesn't verify digital signature of CRL files
daemon@ATHENA.MIT.EDU (Thomas Walpuski)
Wed Aug 11 12:03:24 2004
Date: Wed, 11 Aug 2004 06:52:34 +0000
From: Thomas Walpuski <thomas-bugtraq@unproved.org>
To: bugtraq@securityfocus.com
Message-ID: <20040811065234.GA8681@unproved.org>
Mail-Followup-To: bugtraq@securityfocus.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040810182507.GA15318@acm.jhu.edu>
* Jack Lloyd wrote:
> If Windows is not checking the signature, not only can you remove or alter
> revocations, you can also add ones.
Microsoft's CryptoAPI does check the CRL's signature. It just does not
check it on retrieval, but in the process of verifying certificates.
> Oddly, I couldn't find any language in RFC 3280 that actually requires
> verifying the signature in a CRL. Strange.
RFC 3280, 6.3.3 CRL Processing:
For each distribution point (DP) in the certificate CRL distribution
points extension, for each corresponding CRL in the local CRL cache,
while ((reasons_mask is not all-reasons) and (cert_status is
UNREVOKED)) perform the following:
[..]
(f) Obtain and validate the certification path for the complete CRL
issuer. If a key usage extension is present in the CRL issuer's
certificate, verify that the cRLSign bit is set.
(g) Validate the signature on the complete CRL using the public key
validated in step (f).
That's almost exactly what Microsoft's CryptoAPI does.
Thomas Walpuski
