CVE-2018-1000007: libcurl 7.1 through 7.57.0 might accidentally leak authentication data to third parties.
Noroxi assessment
Priority: Plan (action score 42/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: 9.9% (FIRST EPSS); higher than 95.6% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: curl (Debian:12) 7.58.0-1; curl (Debian:7) 7.26.0-1+wheezy24; curl (Debian:8) 7.38.0-4+deb8u9.
- Mentioned 2 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Add it to your regular patch cycle. Upgrade to curl (Debian:12) 7.58.0-1; curl (Debian:7) 7.26.0-1+wheezy24; curl (Debian:8) 7.38.0-4+deb8u9 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
libcurl 7.1 through 7.57.0 might accidentally leak authentication data to third parties. When asked to send custom headers in its HTTP requests, libcurl will send that set of headers first to the host in the initial URL but also, if asked to follow redirects and a 30X HTTP response code is returned, to the host mentioned in URL in the `Location:` response header value. Sending the same set of headers to subsequent hosts is in particular a problem for applications that pass on custom `Authorization:` headers, as this header often contains privacy sensitive information or data that could allow others to impersonate the libcurl-using client's request.
- Published
- Jan 24, 2018
- Updated
- Jun 16, 2026
- EPSS
- 9.9% · 95th percentile
- CWE
- —
Report tools
Action score
42
Add it to your regular patch cycle.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 3 / 30 · 9.9%
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 |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
| canonical | ubuntu linux | cpe:2.3:o:canonical:ubuntu_linux |
| redhat | enterprise linux desktop | cpe:2.3:o:redhat:enterprise_linux_desktop |
| redhat | enterprise linux server | cpe:2.3:o:redhat:enterprise_linux_server |
| redhat | enterprise linux server aus | cpe:2.3:o:redhat:enterprise_linux_server_aus |
| redhat | enterprise linux server eus | cpe:2.3:o:redhat:enterprise_linux_server_eus |
| redhat | enterprise linux workstation | cpe:2.3:o:redhat:enterprise_linux_workstation |
| fujitsu | m10-1 firmware | cpe:2.3:o:fujitsu:m10-1_firmware |
| fujitsu | m10-1 | cpe:2.3:h:fujitsu:m10-1 |
| fujitsu | m10-4 firmware | cpe:2.3:o:fujitsu:m10-4_firmware |
| fujitsu | m10-4 | cpe:2.3:h:fujitsu:m10-4 |
and 8 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- canonical ubuntu linux12.04
- canonical ubuntu linux14.04
- canonical ubuntu linux16.04
- canonical ubuntu linux17.10
- debian debian linux7.0
- debian debian linux8.0
- debian debian linux9.0
- fujitsu m10-1 firmwarebefore xcp2361
+12 more rows
- fujitsu m10-1 firmwarebefore xcp3070
- fujitsu m10-4 firmwarebefore xcp3070
- fujitsu m10-4 firmwarebefore xcp2361
- fujitsu m10-4s firmwarebefore xcp2361
- fujitsu m10-4s firmwarebefore xcp3070
- fujitsu m12-1 firmwarebefore xcp3070
- fujitsu m12-1 firmwarebefore xcp2361
- fujitsu m12-2 firmwarebefore xcp2361
- fujitsu m12-2 firmwarebefore xcp3070
- fujitsu m12-2s firmwarebefore xcp3070
- fujitsu m12-2s firmwarebefore xcp2361
- haxx curl7.1 and later · up to 7.57.0 inclusive
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.58.0-1 | 7.58.0-1 |
| Debian:7 | curl | before 7.26.0-1+wheezy24 | 7.26.0-1+wheezy24 |
| Debian:8 | curl | before 7.38.0-4+deb8u9 | 7.38.0-4+deb8u9 |
| Debian:9 | curl | before 7.52.1-5+deb9u4 | 7.52.1-5+deb9u4 |
| Red Hat:enterprise_linux:7::client | curl | before 0:7.29.0-51.el7 | 0:7.29.0-51.el7 |
| Red Hat:enterprise_linux:7::client | curl-debuginfo | before 0:7.29.0-51.el7 | 0:7.29.0-51.el7 |
| Red Hat:enterprise_linux:7::client | libcurl | before 0:7.29.0-51.el7 | 0:7.29.0-51.el7 |
| Red Hat:enterprise_linux:7::client | libcurl-devel | before 0:7.29.0-51.el7 | 0:7.29.0-51.el7 |
| Red Hat:enterprise_linux:7::client | nss-pem | before 0:1.0.3-5.el7 | 0:1.0.3-5.el7 |
| Red Hat:enterprise_linux:7::client | nss-pem-debuginfo | before 0:1.0.3-5.el7 | 0:1.0.3-5.el7 |
| Red Hat:rhel_aus:7.4::server | curl | before 0:7.29.0-42.el7_4.2 | 0:7.29.0-42.el7_4.2 |
| Red Hat:rhel_aus:7.4::server | curl-debuginfo | before 0:7.29.0-42.el7_4.2 | 0:7.29.0-42.el7_4.2 |
| Red Hat:rhel_aus:7.4::server | libcurl | before 0:7.29.0-42.el7_4.2 | 0:7.29.0-42.el7_4.2 |
| Red Hat:rhel_aus:7.4::server | libcurl-devel | before 0:7.29.0-42.el7_4.2 | 0:7.29.0-42.el7_4.2 |
| Red Hat:rhel_eus:7.5::computenode | curl | before 0:7.29.0-46.el7_5.1 | 0:7.29.0-46.el7_5.1 |
| Red Hat:rhel_eus:7.5::computenode | curl-debuginfo | before 0:7.29.0-46.el7_5.1 | 0:7.29.0-46.el7_5.1 |
| Red Hat:rhel_eus:7.5::computenode | libcurl | before 0:7.29.0-46.el7_5.1 | 0:7.29.0-46.el7_5.1 |
| Red Hat:rhel_eus:7.5::computenode | libcurl-devel | before 0:7.29.0-46.el7_5.1 | 0:7.29.0-46.el7_5.1 |
| SUSE:Linux Enterprise Desktop 12 SP2 | curl | before 7.37.0-37.14.1 | 7.37.0-37.14.1 |
| SUSE:Linux Enterprise Server 11-SECURITY | curl-openssl1 | before 7.19.7-1.70.13.1 | 7.19.7-1.70.13.1 |
| SUSE:Linux Enterprise Software Development Kit 11 SP4 | curl | before 7.19.7-1.70.13.1 | 7.19.7-1.70.13.1 |
| SUSE:Studio Onsite 1.3 | curl | before 7.19.7-1.20.53.13.1 | 7.19.7-1.20.53.13.1 |
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-2017-8817Nov 29, 2017 · The FTP wildcard function in curl and libcurl before 7.57.0 allows remote attackers to cause a denial of service (out-of-bounds read and…42Plan
- ← EarlierCVE-2017-8818Nov 29, 2017 · curl and libcurl before 7.57.0 on 32-bit platforms allow attackers to cause a denial of service (out-of-bounds access and application…40Plan
- Later →CVE-2017-2628Mar 12, 2018 · curl, as shipped in Red Hat Enterprise Linux 6 before version 7.19.7-53, did not correctly backport the fix for CVE-2015-3148 because it…40Plan
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.58.0-1 · Debian:12 | Package registry (OSV) |
| red hat:curl | 0:7.29.0-51.el7 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:curl-debuginfo | 0:7.29.0-51.el7 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:libcurl | 0:7.29.0-51.el7 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:libcurl-devel | 0:7.29.0-51.el7 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:nss-pem | 0:1.0.3-5.el7 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:nss-pem-debuginfo | 0:1.0.3-5.el7 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| suse:curl | 7.19.7-1.20.53.13.1 · SUSE:Studio Onsite 1.3 | Package registry (OSV) |
| suse:curl-openssl1 | 7.19.7-1.70.13.1 · SUSE:Linux Enterprise Server 11-SECURITY | 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-22-0552 · Aug 15, 2022(RedHat Güvenlik Güncellemesi)
- TR-22-0480 · Jul 6, 2022(RedHat Güvenlik Güncellemesi)
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 (13 more)Show less
- www.securitytracker.com/id/1040274
- access.redhat.com/errata/RHBA-2019:0327
- access.redhat.com/errata/RHSA-2018:3157
- access.redhat.com/errata/RHSA-2018:3558
- access.redhat.com/errata/RHSA-2019:1543
- access.redhat.com/errata/RHSA-2020:0544
- access.redhat.com/errata/RHSA-2020:0594
- curl.haxx.se/docs/adv_2018-b3bf.html
- lists.debian.org/debian-lts-announce/2018/01/msg00038.html
- usn.ubuntu.com/3554-1/
- usn.ubuntu.com/3554-2/
- www.debian.org/security/2018/dsa-4098
- www.oracle.com/technetwork/security-advisory/cpuoct2019-5072832.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.