CVE-2014-3613: cURL and libcurl before 7.38.0 does not properly handle IP addresses in cookie domain names, which allows remote attackers to set cookies…
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 7.1% (FIRST EPSS); higher than 94.3% of all records.
- No special conditions are required; it is repeatable.
- Fixed version: curl (Debian:12) 7.38.0-1; curl (Debian:6.0) 7.21.0-2.1+squeeze9; curl (Debian:7) 7.26.0-1+wheezy10.
Low priority for now. Upgrade to curl (Debian:12) 7.38.0-1; curl (Debian:6.0) 7.21.0-2.1+squeeze9; curl (Debian:7) 7.26.0-1+wheezy10 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
cURL and libcurl before 7.38.0 does not properly handle IP addresses in cookie domain names, which allows remote attackers to set cookies for or send arbitrary cookies to certain sites, as demonstrated by a site at 192.168.0.1 setting cookies for a site at 127.168.0.1.
- Published
- Nov 18, 2014
- Updated
- Jun 16, 2026
- EPSS
- 7.1% · 94th percentile
- CWE
- CWE-310
Report tools
Action score
22
Low priority for now.
- CVSS
- 20 / 40 · 5.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 2 / 30 · 7.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| haxx | curl | cpe:2.3:a:haxx:curl |
| haxx | libcurl | cpe:2.3:a:haxx:libcurl |
| apple | mac os x | cpe:2.3:o:apple:mac_os_x |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- apple mac os xup to 10.10.4 inclusive
- haxx curlup to 7.37.1 inclusive
- haxx curl7.31.0
- haxx curl7.32.0
- haxx curl7.33.0
- haxx curl7.34.0
- haxx curl7.35.0
- haxx curl7.36.0
+9 more rows
- haxx curl7.37.0
- haxx libcurlup to 7.37.1 inclusive
- haxx libcurl7.31.0
- haxx libcurl7.32.0
- haxx libcurl7.33.0
- haxx libcurl7.34.0
- haxx libcurl7.35.0
- haxx libcurl7.36.0
- haxx libcurl7.37.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | curl | before 7.38.0-1 | 7.38.0-1 |
| Debian:6.0 | curl | before 7.21.0-2.1+squeeze9 | 7.21.0-2.1+squeeze9 |
| Debian:7 | curl | before 7.26.0-1+wheezy10 | 7.26.0-1+wheezy10 |
| openSUSE:Tumbleweed | curl | before 7.51.0-1.1 | 7.51.0-1.1 |
| Red Hat:enterprise_linux:6::client | curl | before 0:7.19.7-46.el6 | 0:7.19.7-46.el6 |
| Red Hat:enterprise_linux:6::client | curl-debuginfo | before 0:7.19.7-46.el6 | 0:7.19.7-46.el6 |
| Red Hat:enterprise_linux:6::client | libcurl | before 0:7.19.7-46.el6 | 0:7.19.7-46.el6 |
| Red Hat:enterprise_linux:6::client | libcurl-devel | before 0:7.19.7-46.el6 | 0:7.19.7-46.el6 |
| Red Hat:enterprise_linux:7::client | curl | before 0:7.29.0-25.el7 | 0:7.29.0-25.el7 |
| Red Hat:enterprise_linux:7::client | curl-debuginfo | before 0:7.29.0-25.el7 | 0:7.29.0-25.el7 |
| Red Hat:enterprise_linux:7::client | libcurl | before 0:7.29.0-25.el7 | 0:7.29.0-25.el7 |
| Red Hat:enterprise_linux:7::client | libcurl-devel | before 0:7.29.0-25.el7 | 0:7.29.0-25.el7 |
Same product
haxx: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-22901curl 7.75.0 through 7.76.1 suffers from a use-after-free vulnerability resulting in already freed memory being used when a TLS 1.3 session…51Plan
- CVE-2023-38039When curl retrieves an HTTP response, it stores the incoming headers so that
they can be accessed later via the libcurl headers API.47Plan
- CVE-2024-2398HTTP/2 push headers memory-leak45Plan
Published before and after this one in the same product
- ← EarlierCVE-2014-0139Apr 15, 2014 · cURL 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…24Monitor
- ← EarlierCVE-2014-2522Apr 18, 2014 · curl and libcurl 7.27.0 through 7.35.0, when running on Windows and using the SChannel/Winssl TLS backend, does not verify that the server…17Monitor
- Later →CVE-2014-3620Nov 18, 2014 · cURL and libcurl before 7.38.0 allow remote attackers to bypass the Same Origin Policy and set cookies for arbitrary sites by setting a…21Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:curl | 7.38.0-1 · Debian:12 | Package registry (OSV) |
| opensuse:curl | 7.51.0-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:curl | 0:7.19.7-46.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:curl-debuginfo | 0:7.19.7-46.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:libcurl | 0:7.19.7-46.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:libcurl-devel | 0:7.19.7-46.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- P · data or configuration can be modified
- Availability
- none
- Attack complexity
- Low
- Confidentiality impact
- None
- Integrity impact
- P
- Availability impact
- None
Weakness class (CWE)
CWE-310 · Cryptographic IssuesCVSS vector
AV:N/AC:L/Au:N/C:N/I:P/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (10 more)Show less
- kb.juniper.net/InfoCenter/index?page=content&id=JSA10743
- lists.apple.com/archives/security-announce/2015/Aug/msg00001.html
- lists.opensuse.org/opensuse-security-announce/2014-09/msg00024.html
- rhn.redhat.com/errata/RHSA-2015-1254.html
- www.debian.org/security/2014/dsa-3022
- www.oracle.com/technetwork/security-advisory/cpuoct2017-3236626.html
- www.oracle.com/technetwork/topics/security/cpujul2015-2367936.html
- www.oracle.com/technetwork/topics/security/linuxbulletinoct2015-2719645.html
- www.securityfocus.com/bid/69748
- support.apple.com/kb/HT205031
Vendor advisories and official records. Exploit/PoC links are deliberately left out.