dbcve.org
CurlApplication · Haxx

CVE-2015-3143

MEDIUM · 5.0 CVSS v2.0 Published 2015-04-24
Fix available
A fix is available. Upgrade to after 10.9.5 or later.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
cURL and libcurl 7.10.6 through 7.41.0 does not properly re-use NTLM connections, which allows remote attackers to connect as other users via an unauthenticated request, a similar issue to CVE-2014-0015.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This vulnerability in cURL and libcurl versions 7.10.6-7.41.0 stems from improper NTLM connection reuse. When the library establishes an NTLM-authenticated connection and attempts to reuse it for subsequent requests, it fails to properly manage connection state. This can allow an unauthenticated attacker to inherit the authenticated session context and connect as other users, similar to CVE-2014-0015.

MitigationUpgrade cURL/libcurl to version 7.42.0 or later to obtain the patched version that properly handles NTLM connection state and reuse.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CurlApplication
Affected:= 7.10.6= 7.10.7= 7.10.8= 7.11.0= 7.11.1= 7.11.2= 7.12.0= 7.12.1= 7.12.2= 7.12.3= 7.13.0= 7.13.1
Ubuntu LinuxOperating system
Affected:= 12.04= 14.04= 14.10= 15.04
Debian LinuxOperating system
Affected:= 7.0
LibcurlApplication
Affected:= 7.10.6= 7.10.7= 7.10.8= 7.11.0= 7.11.1= 7.11.2= 7.12.0= 7.12.1= 7.12.2= 7.12.3= 7.13.0= 7.13.1
System Management HomepageApplication
Affected:<= 7.5.3.1
Mac Os XOperating system
Affected:<= 10.9.5= 10.10.0= 10.10.1= 10.10.2= 10.10.3= 10.10.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
None
Integrity
Partial
Availability
None

AV:N/AC:L/Au:N/C:N/I:P/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine cURL version
    Run 'curl --version' or 'curl -V' to display the installed cURL version
    Affected if Version displayed is between 7.10.6 and 7.41.0 inclusive, or matches any of: 7.10.6, 7.10.7, 7.10.8, 7.11.0, 7.11.1, 7.11.2, 7.12.0, 7.12.1, 7.12.2, 7.12.3, 7.13.0, 7.13.1
  2. Determine libcurl version
    Check the libcurl library version via 'pkg-config --modversion libcurl' or inspect the shared library file 'libcurl.so' or 'libcurl.dylib' for its version metadata
    Affected if Version displayed is between 7.10.6 and 7.41.0 inclusive, or matches any of the specific affected versions listed for libcurl
  3. Identify OS packaging
    Check the operating system version (for Ubuntu: 'lsb_release -a'; for Debian: 'cat /etc/debian_version'; for HP SMH: check installed package version; for macOS: 'sw_vers')
    Affected if System is Ubuntu 12.04, 14.04, 14.10, or 15.04; Debian 7.0; HP System Management Homepage 7.5.3.1 or earlier; macOS 10.9.5 or earlier, or macOS 10.10.0 through 10.10.4
  4. Verify NTLM authentication usage
    Inspect application or service configurations for NTLM authentication with cURL/libcurl (search for 'NTLM', 'NTLMv2', or '--ntlm' flag usage in scripts, configs, or code that invokes curl)
    Affected if NTLM authentication is enabled or used with the vulnerable cURL/libcurl version

Environment is affected if cURL or libcurl version is 7.10.6 through 7.41.0 AND the system uses NTLM authentication for HTTP connections.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 10.9.5
Interim mitigation

Upgrade cURL/libcurl to version 7.42.0 or later to obtain the patched version that properly handles NTLM connection state and reuse.

Fix this in Curl Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,540
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-3143 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-3143 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data