CVE-2017-7668

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2022-04-30. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
7.5
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • 9 internet-exposed hosts are running an affected version right now
  • High exploitation likelihood — EPSS 57%
CISA-KEV: Not listedEPSS: 57%CVSS: 7.5Exploit: NoneExposed: 9

A fix is available — apply it.

The HTTP strict parsing changes added in Apache httpd 2.2.32 and 2.4.24 introduced a bug in token list parsing, which allows ap_find_token() to search past the end of its input string. By maliciously crafting a sequence of request headers, an attacker may be able to cause a segmentation fault, or to force ap_find_token() to return an incorrect value.

Live · internet exposure

9 internet-exposed hosts are running an affected version of CVE-2017-7668 right now.

across 5 countries (United States, France, Germany, Canada, Ireland)top: http_server
See the live KEV-Exposure radar →Found passively from public internet-scan data — aggregate, host-redacted.

EchelonGraph is the only CVE feed that fuses live vulnerability intelligence with its own live internet-exposure radar — so you see not just that a CVE is exploited, but how much of the internet is exposed to it right now.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
99.0%
KEV
Not listed

Published

June 20, 2017

Last Modified

May 13, 2026

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuapache2-bin (2.4.25-3ubuntu2.1) @ zesty2026-05-22ubuntu
ubuntuapache2.2-bin (2.2.22-1ubuntu1.12) @ precise2026-05-22ubuntu
redhathttpd-0:2.4.6-40.el7_2.62017-11-13redhat
redhathttpd-0:2.4.6-45.el7_3.52017-11-13redhat
redhathttpd24-httpd-0:2.4.25-9.el7.12017-08-16redhat
redhathttpd-0:2.4.6-67.el7_4.22017-08-15redhat

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.

All Vendor Advisories

(6)

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2017-7668?
CVE-2017-7668 is a high vulnerability published on June 20, 2017. The HTTP strict parsing changes added in Apache httpd 2.2.32 and 2.4.24 introduced a bug in token list parsing, which allows apfindtoken() to search past the end of its input string. By maliciously crafting a sequence of request headers, an attacker may be able to cause a segmentation fault, or to…
When was CVE-2017-7668 disclosed?
CVE-2017-7668 was first published in the National Vulnerability Database on June 20, 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-7668 actively exploited?
CVE-2017-7668 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2017-7668?
CVE-2017-7668 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2017-7668?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-7668, 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-7668

Explore →

Is Your Infrastructure Affected by CVE-2017-7668?

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