CVE-2017-7407: The ourWriteOut function in tool_writeout.c in curl 7.53.1 might allow physically proximate attackers to obtain sensitive information from…
Noroxi assessment
Priority: Monitor (action score 9/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: 0.58% (FIRST EPSS).
- Physical access to the device is required. 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.53.1-r2; curl (Alpine:v3.2) 7.52.1-r1; curl (Alpine:v3.4) 7.52.1-r2.
Low priority for now. Upgrade to curl (Alpine:v3.10) 7.53.1-r2; 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
The ourWriteOut function in tool_writeout.c in curl 7.53.1 might allow physically proximate attackers to obtain sensitive information from process memory in opportunistic circumstances by reading a workstation screen during use of a --write-out argument ending in a '%' character, which leads to a heap-based buffer over-read.
- Published
- Apr 3, 2017
- Updated
- Jun 16, 2026
- EPSS
- 0.5% · 48th percentile
- CWE
- CWE-119
Report tools
Action score
9
Low priority for now.
- CVSS
- 9 / 40 · 2.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
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 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- haxx curl7.53.1
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.53.1-r2 | 7.53.1-r2 |
| 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-4 | 7.52.1-4 |
| Debian:7 | curl | before 7.26.0-1+wheezy19 | 7.26.0-1+wheezy19 |
| SUSE:Linux Enterprise Desktop 12 SP1 | curl | before 7.37.0-36.1 | 7.37.0-36.1 |
| SUSE:Linux Enterprise Server 11-SECURITY | curl-openssl1 | before 7.19.7-1.69.1 | 7.19.7-1.69.1 |
| SUSE:Linux Enterprise Server 11-SECURITY | curl-openssl1 | before 7.19.7-1.70.3.1 | 7.19.7-1.70.3.1 |
| SUSE:Linux Enterprise Software Development Kit 11 SP4 | curl | before 7.19.7-1.69.1 | 7.19.7-1.69.1 |
| SUSE:Linux Enterprise Software Development Kit 11 SP4 | curl | before 7.19.7-1.70.3.1 | 7.19.7-1.70.3.1 |
| SUSE:Studio Onsite 1.3 | curl | before 7.19.7-1.20.52.2 | 7.19.7-1.20.52.2 |
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-2016-3739May 20, 2016 · The (1) mbed_connect_step1 function in lib/vtls/mbedtls.c and (2) polarssl_connect_step1 function in lib/vtls/polarssl.c in cURL and…23Monitor
- ← EarlierCVE-2016-4802Jun 24, 2016 · Multiple untrusted search path vulnerabilities in cURL and libcurl before 7.49.1, when built with SSPI or telnet is enabled, allow local…31Monitor
- Later →CVE-2017-9502Jun 14, 2017 · In curl before 7.54.1 on Windows and DOS, libcurl's default protocol function, which is the logic that allows an application to set which…22Monitor
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.53.1-r2 · Alpine:v3.10 | Package registry (OSV) |
| debian:curl | 7.52.1-4 · Debian:12 | Package registry (OSV) |
| suse:curl | 7.37.0-36.1 · SUSE:Linux Enterprise Desktop 12 SP1 | Package registry (OSV) |
| suse:curl-openssl1 | 7.19.7-1.69.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.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Physical access to the device is required.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Physical
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-119 · Improper Restriction of Operations within the Bounds of a Memory BufferCVSS vector
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
nvd-secondary
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)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Overflow BuffersCAPEC-100likelihood: High · Very High
- Buffer ManipulationCAPEC-123likelihood: High · Very High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
- Filter Failure through Buffer OverflowCAPEC-24likelihood: High · High
- MIME ConversionCAPEC-42likelihood: High · High
- Overflow Binary Resource FileCAPEC-44likelihood: High · Very High
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.