CurlApplication · Haxx
CVE-2014-0139
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 · uneditedcURL and libcurl 7.1 before 7.36.0, when using the OpenSSL, axtls, qsossl or gskit libraries for TLS, recognize a wildcard IP address in the subject's Common Name (CN) field of an X.509 certificate, which might allow man-in-the-middle attackers to spoof arbitrary SSL servers via a crafted certificate issued by a legitimate Certification Authority.
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 confidencecURL and libcurl versions before 7.36.0 improperly accept wildcard patterns in the Common Name (CN) field of X.509 certificates when the CN contains an IP address. This violates RFC 2818, which specifies that IP addresses must not be matched using wildcard patterns. An attacker with a legitimate CA-issued certificate for one IP address could craft a certificate to impersonate other SSL servers.
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= 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- None
AV:N/AC:M/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.
-
Check cURL command-line tool versionRun 'curl --version' or check the binary file version using 'file $(which curl)' and compare against the version stringAffected if The version shown is between 7.10.6 and 7.13.1 inclusive
-
Check libcurl library versionRun 'curl-config --version' or examine the linked libcurl library file (often in /usr/lib/ or found via 'ldd $(which curl)')Affected if The libcurl version is between 7.10.6 and 7.13.1 inclusive
-
Verify SSL/TLS usage in your environmentSearch configuration files, scripts, or application code that use curl/libcurl for HTTPS or other SSL-based connections (look for -k/--insecure flags or CURLOPT_SSL_VERIFYHOST CURLOPT_SSL_VERIFYPEER usage)Affected if Your applications or scripts use cURL/libcurl to connect to servers over SSL/TLS where the target may be specified by IP address
You are affected if your installed cURL or libcurl version falls within 7.10.6 to 7.13.1 and you use it for SSL/TLS connections to servers identified by IP address.
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 cURL/libcurl to version 7.36.0 or later, which correctly rejects wildcard patterns in certificate CN fields when the CN contains an IP address.
Fix this in Curl
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,288.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0139 — 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-0139 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