CVE-2017-1000257: An IMAP FETCH response line indicates the size of the returned data, in number of bytes.
Noroxi assessment
Priority: Monitor (action score 38/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: 6.2% (FIRST EPSS); higher than 93.5% 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.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: curl (Alpine:v3.10) 7.56.1-r0; curl (Alpine:v3.3) 7.55.0-r2; curl (Debian:12) 7.56.1-1.
Low priority for now. Upgrade to curl (Alpine:v3.10) 7.56.1-r0; curl (Alpine:v3.3) 7.55.0-r2; curl (Debian:12) 7.56.1-1 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
An IMAP FETCH response line indicates the size of the returned data, in number of bytes. When that response says the data is zero bytes, libcurl would pass on that (non-existing) data with a pointer and the size (zero) to the deliver-data function. libcurl's deliver-data function treats zero as a magic number and invokes strlen() on the data to figure out the length. The strlen() is called on a heap based buffer that might not be zero terminated so libcurl might read beyond the end of it into whatever memory lies after (or just crash) and then deliver that to the application as if it was actually downloaded.
- Published
- Oct 31, 2017
- Updated
- Jun 16, 2026
- EPSS
- 6.2% · 93th percentile
- CWE
- CWE-119
Report tools
Action score
38
Monitor
Low priority for now.
- CVSS
- 36 / 40 · 9.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 2 / 30 · 6.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- 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.
Running WordPress? Scan your site free with WP Lens
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 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.
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux8.0
- debian debian linux9.0
- haxx libcurl7.20.0 and later · up to 7.56.0 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.56.1-r0 | 7.56.1-r0 |
| Alpine:v3.3 | curl | before 7.55.0-r2 | 7.55.0-r2 |
| Debian:12 | curl | before 7.56.1-1 | 7.56.1-1 |
| Debian:7 | curl | before 7.26.0-1+wheezy22 | 7.26.0-1+wheezy22 |
| Debian:8 | curl | before 7.38.0-4+deb8u7 | 7.38.0-4+deb8u7 |
| Debian:9 | curl | before 7.52.1-5+deb9u2 | 7.52.1-5+deb9u2 |
| openSUSE:Tumbleweed | curl | before 7.79.1-1.1 | 7.79.1-1.1 |
| Red Hat:enterprise_linux:7::client | curl | before 0:7.29.0-42.el7_4.1 | 0:7.29.0-42.el7_4.1 |
| Red Hat:enterprise_linux:7::client | curl-debuginfo | before 0:7.29.0-42.el7_4.1 | 0:7.29.0-42.el7_4.1 |
| Red Hat:enterprise_linux:7::client | libcurl | before 0:7.29.0-42.el7_4.1 | 0:7.29.0-42.el7_4.1 |
| Red Hat:enterprise_linux:7::client | libcurl-devel | before 0:7.29.0-42.el7_4.1 | 0:7.29.0-42.el7_4.1 |
| SUSE:Linux Enterprise Desktop 12 SP2 | curl | before 7.37.0-37.8.1 | 7.37.0-37.8.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.63This 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-1000100Oct 4, 2017 · When doing a TFTP transfer and curl/libcurl is given a URL that contains a very long file name (longer than about 515 bytes), the file name 27Monitor
- ← EarlierCVE-2017-1000254Oct 6, 2017 · libcurl may read outside of a heap allocated buffer when doing FTP.32Monitor
- Later →CVE-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
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.56.1-r0 · Alpine:v3.10 | Package registry (OSV) |
| debian:curl | 7.56.1-1 · Debian:12 | Package registry (OSV) |
| opensuse:curl | 7.79.1-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:curl | 0:7.29.0-42.el7_4.1 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:curl-debuginfo | 0:7.29.0-42.el7_4.1 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:libcurl | 0:7.29.0-42.el7_4.1 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:libcurl-devel | 0:7.29.0-42.el7_4.1 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| suse:curl | 7.37.0-37.8.1 · SUSE:Linux Enterprise Desktop 12 SP2 | 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.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
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
- none
- 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
- None
- Availability impact
- High
Weakness class (CWE)
CWE-119 · Improper Restriction of Operations within the Bounds of a Memory BufferCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.