GnuTLS insufficient cert verification Vulnerability
Project curl Security Advisory, July 10th 2007 permalink
libcurl (when built to use GnuTLS) fails to verify that a peer's certificate hasn't already expired or hasn't yet become valid. This allows malicious servers to present certificates to libcurl that won't be rejected properly.
Notably, the cacert and common name checks are still in place which reduces the risk for random servers to take advantage of this flaw.
There is no known exploit at the time of this writing.
The Common Vulnerabilities and Exposures (CVE) project has assigned the name CVE-2007-3564 to this issue.
CWE-298: Improper Validation of Certificate Expiration
- Affected versions: curl and libcurl 7.14.0 to and including 7.16.3
- Not affected versions: curl and libcurl 7.13.2 and earlier, 7.16.4 and later
Note that libcurl needs to be built to use GnuTLS for this flaw to be in effect.
Also note that (lib)curl is used by many applications, and not always advertised as such.
We suggest you take one of the following actions immediately, in order of preference:
A - Upgrade to curl and libcurl 7.16.4
B - Apply the patch https://curl.se/libcurl-gnutlscert.patch to your libcurl version and install this
C - Build curl with SSL provided by another library, like OpenSSL or NSS
D - Build curl with SSL disabled
We were notified by Kees Cook on June 27th, 2007. His notification email contained a valid patch.
We agreed on and coordinated the synchronous disclosure of this problem together with the curl 7.16.4 release.
curl 7.16.4 was released on July 10 2007, just before this flaw was publicly disclosed.
- Reported-by: Kees Cook
- Patched-by: Daniel Stenberg
Thanks a lot!