CVE-2017-1000257

CRITICALNVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2022-05-14. NVD baseline CVSS 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
9.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 6%CVSS: 9.1Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
9.1
EG Score
9.1(medium)
EPSS
92.7%
KEV
Not listed

Published

October 31, 2017

Last Modified

May 13, 2026

Advisory Details (8)

Auto-updated May 22, 2026
Patch available. Sources: redhat.
generic
http://www.securityfocus.com/bid/101519
generic

[SECURITY] [DSA 4007-1] curl security update

http://www.debian.org/security/2017/dsa-4007
generic

cURL: Multiple vulnerabilities (GLSA 201712-04) — Gentoo security

https://security.gentoo.org/glsa/201712-04
generic

curl - IMAP FETCH response out of bounds read - CVE-2017-1000257

https://curl.haxx.se/docs/adv_20171023.html
redhat Patch Available

Affected: Red Hat Enterprise Linux 7. (BZ#1640722)

https://access.redhat.com/errata/RHSA-2018:3558
redhat Patch Available
https://access.redhat.com/errata/RHSA-2018:2486
redhat Patch Available

Affected: Red Hat Enterprise Linux 7.

https://access.redhat.com/errata/RHSA-2017:3263
generic
http://www.securitytracker.com/id/1039644

Vendor Advisories for CVE-2017-1000257(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibcurl3 (7.22.0-3ubuntu4.18) @ precise2026-05-22ubuntu
ubuntulibcurl3-nss (7.52.1-4ubuntu1.3) @ zesty2026-05-22ubuntu
redhathttpd24-nghttp2-0:1.7.1-7.el72018-11-13redhat
redhatjbcs-httpd24-curl2018-08-16redhat
redhatcurl-0:7.29.0-42.el7_4.12017-11-27redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Additional Vendor Advisories

(4)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 10× in last 7d / 37× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-07 13:42 UTCEPSS rescore
  2. 2026-07-06 16:24 UTCEPSS rescore
  3. 2026-07-06 16:24 UTCEPSS rescore
  4. 2026-07-06 02:20 UTCEPSS rescore
  5. 2026-07-06 02:20 UTCEPSS rescore
  6. 2026-07-05 02:27 UTCEPSS rescore
  7. 2026-07-04 06:28 UTCEPSS rescore
  8. 2026-07-01 15:02 UTCEPSS rescore
  9. 2026-06-30 23:19 UTCEPSS rescore
  10. 2026-06-30 23:19 UTCEPSS rescore
  11. 2026-06-28 14:04 UTCEPSS rescore
  12. 2026-06-28 04:53 UTCEPSS rescore
  13. 2026-06-27 03:05 UTCEPSS rescore
  14. 2026-06-25 13:47 UTCEPSS rescore
  15. 2026-06-24 14:02 UTCEPSS rescore
  16. 2026-06-23 21:30 UTCEPSS rescore
  17. 2026-06-22 22:05 UTCOSV refresh
  18. 2026-06-22 14:23 UTCEPSS rescore
  19. 2026-06-21 14:54 UTCEPSS rescore
  20. 2026-06-21 14:54 UTCEPSS rescore
  21. 2026-06-21 01:57 UTCEPSS rescore
  22. 2026-06-21 01:57 UTCEPSS rescore
  23. 2026-06-19 19:23 UTCEPSS rescore
  24. 2026-06-19 19:23 UTCEPSS rescore
  25. 2026-06-18 17:50 UTCEPSS rescore
Show 50 more
  1. 2026-06-18 17:50 UTCEPSS rescore
  2. 2026-06-17 17:50 UTCEPSS rescore
  3. 2026-06-17 17:50 UTCEPSS rescore
  4. 2026-06-16 17:50 UTCEPSS rescore
  5. 2026-06-15 17:45 UTCEPSS rescore
  6. 2026-06-14 23:14 UTCEPSS rescore
  7. 2026-06-14 23:14 UTCEPSS rescore
  8. 2026-06-13 22:57 UTCEPSS rescore
  9. 2026-06-13 22:57 UTCEPSS rescore
  10. 2026-06-12 23:09 UTCEPSS rescore
  11. 2026-06-11 13:57 UTCEPSS rescore
  12. 2026-06-08 14:14 UTCEPSS rescore
  13. 2026-06-07 15:22 UTCEPSS rescore
  14. 2026-06-07 15:22 UTCEPSS rescore
  15. 2026-06-06 13:45 UTCEPSS rescore
  16. 2026-06-06 13:45 UTCEPSS rescore
  17. 2026-06-05 22:44 UTCEPSS rescore
  18. 2026-06-05 14:27 UTCOSV refresh
  19. 2026-06-05 06:08 UTCEPSS rescore
  20. 2026-06-05 06:08 UTCEPSS rescore
  21. 2026-06-04 13:10 UTCEPSS rescore
  22. 2026-06-04 13:10 UTCEPSS rescore
  23. 2026-06-02 20:10 UTCEPSS rescore
  24. 2026-06-01 13:49 UTCEPSS rescore
  25. 2026-06-01 13:49 UTCEPSS rescore
  26. 2026-05-31 22:28 UTCEPSS rescore
  27. 2026-05-31 22:28 UTCEPSS rescore
  28. 2026-05-31 00:14 UTCEPSS rescore
  29. 2026-05-29 13:41 UTCEPSS rescore
  30. 2026-05-28 13:42 UTCEPSS rescore
  31. 2026-05-28 13:42 UTCEPSS rescore
  32. 2026-05-27 13:38 UTCEPSS rescore
  33. 2026-05-27 13:38 UTCEPSS rescore
  34. 2026-05-26 13:42 UTCEPSS rescore
  35. 2026-05-26 13:42 UTCEPSS rescore
  36. 2026-05-26 07:17 UTCEPSS rescore
  37. 2026-05-24 16:44 UTCEPSS rescore
  38. 2026-05-22 21:15 UTCEPSS rescore
  39. 2026-05-22 08:22 UTCEG score recompute
  40. 2026-05-22 08:22 UTCVendor advisory
  41. 2026-05-22 08:22 UTCGHSA enrichment
  42. 2026-05-20 22:37 UTCEPSS rescore
  43. 2026-05-20 22:37 UTCEPSS rescore
  44. 2026-05-20 22:37 UTCEPSS rescore
  45. 2026-05-20 11:21 UTCEPSS rescore
  46. 2026-05-20 11:21 UTCEPSS rescore
  47. 2026-05-19 16:33 UTCOSV refresh
  48. 2026-05-18 21:30 UTCEPSS rescore
  49. 2026-05-18 21:30 UTCEPSS rescore
  50. 2026-05-18 21:30 UTCEPSS rescore

Frequently asked(5)

What is CVE-2017-1000257?
CVE-2017-1000257 is a critical vulnerability published on October 31, 2017. 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…
When was CVE-2017-1000257 disclosed?
CVE-2017-1000257 was first published in the National Vulnerability Database on October 31, 2017, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-1000257 actively exploited?
CVE-2017-1000257 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 92.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2017-1000257?
CVE-2017-1000257 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2017-1000257?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-1000257, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2017-1000257

Explore →

Is Your Infrastructure Affected by CVE-2017-1000257?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs