CurlApplication · Haxx
CVE-2014-0138
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 · uneditedThe default configuration in cURL and libcurl 7.10.6 before 7.36.0 re-uses (1) SCP, (2) SFTP, (3) POP3, (4) POP3S, (5) IMAP, (6) IMAPS, (7) SMTP, (8) SMTPS, (9) LDAP, and (10) LDAPS connections, which might allow context-dependent attackers to connect as other users via a 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 · high confidenceThe default configuration in cURL and libcurl 7.10.6 through 7.35.0 re-uses existing network connections for SCP, SFTP, POP3, POP3S, IMAP, IMAPS, SMTP, SMTPS, LDAP, and LDAPS protocols. This can allow context-dependent attackers to connect as other users by leveraging a connection previously authenticated by a different user, a similar issue to CVE-2014-0015.
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
= 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
Debian LinuxOperating system
= 7.0= 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.1CVSS 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
- Partial
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:P/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed cURL versionRun `curl --version` to see the exact version number of the cURL command-line toolAffected if The version shown is 7.10.6 through 7.35.0 inclusive
-
Identify libcurl library versionRun `curl-config --version` or check your application's linked libcurl version via `ldd /path/to/your/application` and look for libcurlAffected if The libcurl library version is 7.10.6 through 7.35.0 inclusive
-
Check Debian curl package versionOn Debian-based systems, run `dpkg -l | grep curl` or `apt-cache policy curl` to see the installed package versionAffected if The installed package version corresponds to cURL 7.10.6 through 7.35.0 on Debian 7.0
-
Determine if affected protocols are in useReview any scripts, applications, or services that use libcurl and connect via SCP, SFTP, POP3, POP3S, IMAP, IMAPS, SMTP, SMTPS, LDAP, or LDAPS protocolsAffected if The affected version is installed AND any of these protocols are used for authenticated connections
You are affected if you have cURL or libcurl version 7.10.6 through 7.35.0 and use any of the listed protocols (SCP, SFTP, POP3, IMAP, SMTP, LDAP, etc.) for authenticated connections where connection pooling could cause credentials to be reused across different users.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade to cURL/libcurl 7.36.0 or later where connection re-use is disabled by default for these sensitive protocols, or explicitly configure the library to disable connection pooling/re-use.
Fix this in Curl
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0138 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-0138 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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