cURL and libcurl 7.10.6 through 7.34.0, when more than one authentication method is enabled, re-uses NTLM connections, which might allow context-dependent attackers to authenticate as other users via a request.
The MITRE CVE dictionary describes this issue as:
Find out more about CVE-2014-0015 from the MITRE CVE dictionary dictionary and NIST NVD.
This issue affects the version of curl as shipped with Red Hat Enterprise Linux 5 and 7. The Red Hat Security Response Team has rated this issue as having Moderate security impact, a future update may address this flaw.
| Base Score | 4.3 |
|---|---|
| Base Metrics | AV:N/AC:M/Au:N/C:P/I:N/A:N |
| Access Vector | Network |
| Access Complexity | Medium |
| Authentication | None |
| Confidentiality Impact | Partial |
| Integrity Impact | None |
| Availability Impact | None |
Find out more about Red Hat support for the Common Vulnerability Scoring System (CVSS).
| Platform | Errata | Release Date |
|---|---|---|
| Red Hat Enterprise Linux 6 (curl) | RHSA-2014:0561 | 2014-05-27 |
| Platform | Package | State |
|---|---|---|
| Red Hat Enterprise Linux 7 | curl | Not affected |
| Red Hat Enterprise Linux 5 | curl | Will not fix |
Avoid using HTTP NTLM in your application. If you must use NTLM authentication, ensure that it is the only requested authentication method (use --ntlm specifically, do not use --anyauth or other authentication methods).
Vulmon