cURL Initialization Error in CURLcode randit() Generates Weak or Non-Random Numbers
SecurityTracker Alert ID: 1037528|
SecurityTracker URL: http://securitytracker.com/id/1037528
(Links to External Site)
Date: Dec 23 2016
Modification of system information|
Fix Available: Yes Vendor Confirmed: Yes |
Version(s): 7.52.0 only|
A vulnerability was reported in cURL. A remote user may be able to bypass security controls on the target system.|
The CURLcode randit() function does not properly generate random values. As a result, various functions that use ostensibly random values may not function properly, including Digest and NTLM authentication functions.
Kamil Dudka reported this vulnerability.
A remote user may be able to bypass security controls on the target system.|
The vendor has issued a fix (7.52.1).|
The vendor advisory is available at:
Vendor URL: curl.haxx.se/docs/adv_20161223.html (Links to External Site)
|Underlying OS: Linux (Any), UNIX (Any), Windows (Any)|
Source Message Contents
Subject: [oss-security] [SECURITY ADVISORY] curl: uninitialized random|
Project curl Security Advisory, December 23, 2016 -
libcurl's (new) internal function that returns a good 32bit random value was
implemented poorly and overwrote the pointer instead of writing the value into
the buffer the pointer pointed to.
This random value is used to generate nonces for Digest and NTLM
authentication, for generating boundary strings in HTTP formposts and
more. Having a weak or virtually non-existent random there makes these
This function is brand new in 7.52.0 and is the result of an overhaul to make
sure libcurl uses strong random as much as possible - provided by the backend
TLS crypto libraries when present. The faulty function was introduced in [this
We are not aware of any exploit of this flaw.
This mistake managed to slip in because:
1. It wasn't detected by manual code reviews
2. When libcurl is built debug-enabled (which is often the case when libcurl
developers build it), the bug doesn't trigger.
3. When built without -g, the test suite's "valgrind output parser" wrongly
ignored the valgrind output and with libcurl's standard build it is
typically built without -g. Thus hiding this problem to most users.
The Common Vulnerabilities and Exposures (CVE) project has assigned the name
CVE-2016-9594 to this issue.
This flaw exists in the following libcurl versions.
- Affected versions: libcurl 7.52.0 only
- Not affected versions: libcurl < 7.52.0 and libcurl >= 7.52.1
libcurl is used by many applications, but not always advertised as such!
In version 7.52.1, we fixed the function and we fixed the valgrind parser in
the test suite.
A [patch for CVE-2016-9594](https://curl.haxx.se/CVE-2016-9594.patch) is
We suggest you take one of the following actions immediately, in order of
A - Upgrade curl and libcurl to version 7.52.1
B - Apply the patch to 7.52.0 and rebuild
It was first reported to the curl project on December 21 by Kamil Dudka.
We contacted distros@openwall on December 21.
curl 7.52.1 was released on December 23 2016, coordinated with the publication
of this advisory.
Reported and patched by Kamil Dudka.