CVE-2017-7468: In curl and libcurl 7.52.0 to and including 7.53.1, libcurl would attempt to resume a TLS session even if the client certificate had changed
Noroxi assessment
Priority: Monitor (action score 30/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: 1.6% (FIRST EPSS); higher than 77.1% 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 (Alpine:v3.10) 7.54.0-r0; curl (Alpine:v3.2) 7.52.1-r1; curl (Alpine:v3.4) 7.52.1-r2.
- Severity is disputed: the assigning authority (CNA) scores it 4.8, NVD 7.5.
Low priority for now. Upgrade to curl (Alpine:v3.10) 7.54.0-r0; curl (Alpine:v3.2) 7.52.1-r1; curl (Alpine:v3.4) 7.52.1-r2 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
In curl and libcurl 7.52.0 to and including 7.53.1, libcurl would attempt to resume a TLS session even if the client certificate had changed. That is unacceptable since a server by specification is allowed to skip the client certificate check on resume, and may instead use the old identity which was established by the previous certificate (or no certificate). libcurl supports by default the use of TLS session id/ticket to resume previous TLS sessions to speed up subsequent TLS handshakes. They are used when for any reason an existing TLS connection couldn't be kept alive to make the next handshake faster. This flaw is a regression and identical to CVE-2016-5419 reported on August 3rd 2016, but affecting a different version range.
- Published
- Jul 16, 2018
- Updated
- Jun 16, 2026
- EPSS
- 1.6% · 77th percentile
- CWE
- CWE-295
Report tools
Action score
30
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.6%
CNA vs NVD score
- NVD
- 7.5
- CNA · redhat
- 4.8
- 2.7 point gap
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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.
Check your site's encryptionRun the SSL check
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 | libcurl | cpe:2.3:a:haxx:libcurl |
Check your site's encryption
This vulnerability is about certificate validation or weak cryptography. The free SSL checker tests your certificate, enabled TLS versions and weak ciphers.
Run the SSL checkVersions reported by the vendor
Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.
[UNKNOWN] curl
- curl 7.54.0affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- haxx libcurl7.52.0 and later · up to 7.53.1 inclusive
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.10 | curl | before 7.54.0-r0 | 7.54.0-r0 |
| Alpine:v3.2 | curl | before 7.52.1-r1 | 7.52.1-r1 |
| Alpine:v3.4 | curl | before 7.52.1-r2 | 7.52.1-r2 |
| Alpine:v3.5 | curl | before 7.52.1-r3 | 7.52.1-r3 |
| Debian:12 | curl | before 7.52.1-5 | 7.52.1-5 |
| openSUSE:Tumbleweed | curl | before 7.79.1-1.1 | 7.79.1-1.1 |
Same product
haxx: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-38545This flaw makes curl overflow a heap based buffer in the SOCKS5 proxy
handshake.62This week
- CVE-2019-5436A heap buffer overflow in the TFTP receiving code allows for DoS or arbitrary code execution in libcurl versions 7.19.4 through 7.64.1.46Plan
- CVE-2019-3822libcurl versions from 7.36.0 to before 7.64.0 are vulnerable to a stack-based buffer overflow.43Plan
Published before and after this one in the same product
- ← EarlierCVE-2017-1000257Oct 31, 2017 · An IMAP FETCH response line indicates the size of the returned data, in number of bytes.38Monitor
- ← EarlierCVE-2018-1000005Jan 24, 2018 · libcurl 7.49.0 to and including 7.57.0 contains an out bounds read in code handling HTTP/2 trailers.37Monitor
- Later →CVE-2016-8622Jul 31, 2018 · The URL percent-encoding decode function in libcurl before 7.51.0 is called `curl_easy_unescape`.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 |
|---|---|---|
| alpine:curl | 7.54.0-r0 · Alpine:v3.10 | Package registry (OSV) |
| debian:curl | 7.52.1-5 · Debian:12 | Package registry (OSV) |
| opensuse:curl | 7.79.1-1.1 · openSUSE:Tumbleweed | 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
- 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
- none
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-295 · Improper Certificate ValidationCVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
nvd-primary
Root cause
A certificate validation error is silently swallowed instead of terminating the connection. Often, code added for a test environment makes its way into production.
The bug in code
The whole CWE-295 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
override fun checkServerTrusted(chain: Array<X509Certificate>, type: String) {
// Left empty for the test environment
}Fixed
val client = OkHttpClient.Builder()
.certificatePinner(
CertificatePinner.Builder()
.add("api.sirius.example", "sha256/…")
.build()
).build()Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.