CVE-2017-8817

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Elevated
9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 11%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

The FTP wildcard function in curl and libcurl before 7.57.0 allows remote attackers to cause a denial of service (out-of-bounds read and application crash) or possibly have unspecified other impact via a string that ends with an '[' character.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
75
EG Risk 75/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
11%
EPSS %ILE
95th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 29, 2017

Last Modified

June 17, 2026

Advisory Details (7)

Auto-updated Oct 5, 2026
Patch available. Sources: redhat.
Web page

CVE-2017-8817 - PSIRT.COM

http://www.securityfocus.com/bid/102057
Web page

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

https://www.debian.org/security/2017/dsa-4051
Web page

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

https://security.gentoo.org/glsa/201712-04
Web pageMentions a patch (unverified)

[SECURITY] [DLA 1195-1] curl security update

https://lists.debian.org/debian-lts-announce/2017/11/msg00040.html
Web page

curl - FTP wildcard out of bounds read - CVE-2017-8817

https://curl.haxx.se/docs/adv_2017-ae72.html
Red HatMentions a patch (unverified)

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

https://access.redhat.com/errata/RHSA-2018:3558
Web page
http://www.securitytracker.com/id/1039897

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibcurl3 (7.22.0-3ubuntu4.19) @ precise2026-05-20ubuntu
ubuntulibcurl3-nss (7.52.1-4ubuntu1.4) @ zesty2026-05-20ubuntu
redhathttpd24-nghttp2-0:1.7.1-7.el72018-11-13redhat

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.

Affected Packages

(28 across 28 ecosystems)
Alpine:v3.10(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • 7.21.0 up to 7.57.0-r0: fixed in 7.57.0-r0
—
Alpine:v3.11(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • 7.21.0 up to 7.57.0-r0: fixed in 7.57.0-r0
—
Alpine:v3.12(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • 7.21.0 up to 7.57.0-r0: fixed in 7.57.0-r0
—
Alpine:v3.13(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • 7.21.0 up to 7.57.0-r0: fixed in 7.57.0-r0
—
Alpine:v3.14(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • 7.21.0 up to 7.57.0-r0: fixed in 7.57.0-r0
—
Alpine:v3.15(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • 7.21.0 up to 7.57.0-r0: fixed in 7.57.0-r0
—
Alpine:v3.16(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • 7.21.0 up to 7.57.0-r0: fixed in 7.57.0-r0
—
Alpine:v3.17(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • 7.21.0 up to 7.57.0-r0: fixed in 7.57.0-r0
—
Alpine:v3.18(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • 7.21.0 up to 7.57.0-r0: fixed in 7.57.0-r0
—
Alpine:v3.19(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • 7.21.0 up to 7.57.0-r0: fixed in 7.57.0-r0
—
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • 7.21.0 up to 7.57.0-r0: fixed in 7.57.0-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • 7.21.0 up to 7.57.0-r0: fixed in 7.57.0-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • 7.21.0 up to 7.57.0-r0: fixed in 7.57.0-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • 7.21.0 up to 7.57.0-r0: fixed in 7.57.0-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • 7.21.0 up to 7.57.0-r0: fixed in 7.57.0-r0
—
Alpine:v3.4(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • 7.21.0 up to 7.57.0-r0: fixed in 7.57.0-r0
—
Alpine:v3.5(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • 7.21.0 up to 7.57.0-r0: fixed in 7.57.0-r0
—
Alpine:v3.6(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • 7.21.0 up to 7.57.0-r0: fixed in 7.57.0-r0
—
Alpine:v3.7(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • 7.21.0 up to 7.57.0-r0: fixed in 7.57.0-r0
—
Alpine:v3.8(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • 7.21.0 up to 7.57.0-r0: fixed in 7.57.0-r0
—
Alpine:v3.9(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • 7.21.0 up to 7.57.0-r0: fixed in 7.57.0-r0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • every version up to 7.57.0-1: fixed in 7.57.0-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • every version up to 7.57.0-1: fixed in 7.57.0-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • every version up to 7.57.0-1: fixed in 7.57.0-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • every version up to 7.57.0-1: fixed in 7.57.0-1
—
Debian:7(1)
PackageVulnerable rangeFix by version rangeDependents
curl7.26.0-1+wheezy10 ... 7.26.0-1+wheezy9 (21 versions)
  • every version up to 7.26.0-1+wheezy23: fixed in 7.26.0-1+wheezy23
—
Debian:8(1)
PackageVulnerable rangeFix by version rangeDependents
curl7.38.0-4 ... 7.38.0-4+deb8u7 (8 versions)
  • every version up to 7.38.0-4+deb8u8: fixed in 7.38.0-4+deb8u8
—
Debian:9(1)
PackageVulnerable rangeFix by version rangeDependents
curl7.52.1-5, 7.52.1-5+deb9u1, 7.52.1-5+deb9u2
  • every version up to 7.52.1-5+deb9u3: fixed in 7.52.1-5+deb9u3
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(3)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 8× in last 7d / 25× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 84 of 185 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 16 repeat rows among the latest 100 are merged into the row they repeat. The 101 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same vendor + same CWE)· as of October 11, 2026

Frequently asked(5)

What is CVE-2017-8817?
CVE-2017-8817 is a critical-severity vulnerability; its CVE record was published on November 29, 2017. The FTP wildcard function in curl and libcurl before 7.57.0 allows remote attackers to cause a denial of service (out-of-bounds read and application crash) or possibly have unspecified other impact via a string that ends with an '[' character.
When was CVE-2017-8817 made public?
CVE-2017-8817 was made public on November 29, 2017: that is the date its CVE record's CNA, Debian GNU/Linux, gives for when the vulnerability was made public. The CVE record itself was published on November 29, 2017. EchelonGraph's copy of the record carries a last-modified date of June 17, 2026; the record at its source may have been updated since.
Is CVE-2017-8817 actively exploited?
CVE-2017-8817 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 11% probability of exploitation in the next 30 days (95th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2017-8817?
CVE-2017-8817 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2017-8817?
A fix for CVE-2017-8817 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2017-8817

Explore →

Is Your Infrastructure Affected by CVE-2017-8817?

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

Book a Demo →Browse All CVEs