Skip to content
Noroxi
NVD / CVE Program· CNA mitre

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…

LowCVSS 2.4 · v3.1—No exploit Fix available

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

Report tools

JSON

Action score

9

Monitor

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.

Follow CVE-2017-7407

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi 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 help

Affected 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.

VendorProduct
haxxcurl

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.

EcosystemPackageAffected rangeFix
Alpine:v3.10curlbefore 7.53.1-r27.53.1-r2
Alpine:v3.2curlbefore 7.52.1-r17.52.1-r1
Alpine:v3.4curlbefore 7.52.1-r27.52.1-r2
Alpine:v3.5curlbefore 7.52.1-r37.52.1-r3
Debian:12curlbefore 7.52.1-47.52.1-4
Debian:7curlbefore 7.26.0-1+wheezy197.26.0-1+wheezy19
SUSE:Linux Enterprise Desktop 12 SP1curlbefore 7.37.0-36.17.37.0-36.1
SUSE:Linux Enterprise Server 11-SECURITYcurl-openssl1before 7.19.7-1.69.17.19.7-1.69.1
SUSE:Linux Enterprise Server 11-SECURITYcurl-openssl1before 7.19.7-1.70.3.17.19.7-1.70.3.1
SUSE:Linux Enterprise Software Development Kit 11 SP4curlbefore 7.19.7-1.69.17.19.7-1.69.1
SUSE:Linux Enterprise Software Development Kit 11 SP4curlbefore 7.19.7-1.70.3.17.19.7-1.70.3.1
SUSE:Studio Onsite 1.3curlbefore 7.19.7-1.20.52.27.19.7-1.20.52.2

Same product

haxx: all records

Other 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-leak
    45Plan

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 / packageFixed versionSource
alpine:curl7.53.1-r2 · Alpine:v3.10Package registry (OSV)
debian:curl7.52.1-4 · Debian:12Package registry (OSV)
suse:curl7.37.0-36.1 · SUSE:Linux Enterprise Desktop 12 SP1Package registry (OSV)
suse:curl-openssl17.19.7-1.69.1 · SUSE:Linux Enterprise Server 11-SECURITYPackage 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

CVSS vector

CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

nvd-secondary

References

All records