CVE-2017-17742

MEDIUMNVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

Score 5.3 from GitHub Security Advisory published 2022-05-13. NVD baseline CVSS 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 5.5%CVSS: 5.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Ruby before 2.2.10, 2.3.x before 2.3.7, 2.4.x before 2.4.4, 2.5.x before 2.5.1, and 2.6.0-preview1 allows an HTTP Response Splitting attack. An attacker can inject a crafted key and value into an HTTP response for the HTTP server of WEBrick.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
31
EG Risk 31/100CISA SSVC

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
Severity53% × 45%
Exploitation5% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
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
5.5%
EPSS %ILE
92nd
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or 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 (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

April 3, 2018

Last Modified

November 21, 2024

References (40)

Patch Availability(8)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubunturuby2.0-tcltk (2.0.0.484-1ubuntu2.10) @ trusty2026-05-23ubuntu
redhatruby-0:2.0.0.648-37.el7_62020-05-26redhat
redhatruby-0:2.0.0.648-36.el7_42020-05-19redhat
redhatruby-0:2.0.0.648-36.el7_52020-04-29redhat
redhatruby-0:2.0.0.648-36.el72019-08-06redhat
redhatrh-ruby23-ruby-0:2.3.8-69.el72018-11-29redhat
redhatrh-ruby25-ruby-0:2.5.3-6.el72018-11-29redhat
redhatrh-ruby24-ruby-0:2.4.5-91.el72018-11-29redhat

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

(31 across 28 ecosystems)
Debian:7(2)
PackageVulnerable rangeFix by version rangeDependents
ruby1.81.8.7.358-7 ... 1.8.7.358-7.1+deb7u5 (7 versions)
  • every version up to 1.8.7.358-7.1+deb7u6: fixed in 1.8.7.358-7.1+deb7u6
—
ruby1.9.11.9.3.194-8.1 ... 1.9.3.194-8.1+deb7u7 (7 versions)
  • every version up to 1.9.3.194-8.1+deb7u8: fixed in 1.9.3.194-8.1+deb7u8
—
Debian:8(2)
PackageVulnerable rangeFix by version rangeDependents
jruby1.5.6-9, 1.5.6-9+deb8u1
  • every version up to 1.5.6-9+deb8u2: fixed in 1.5.6-9+deb8u2
—
ruby2.12.1.5-2, 2.1.5-2+deb8u1, 2.1.5-2+deb8u2, 2.1.5-2+deb8u3
  • every version up to 2.1.5-2+deb8u4: fixed in 2.1.5-2+deb8u4
—
Debian:9(2)
PackageVulnerable rangeFix by version rangeDependents
jruby1.7.26-1, 1.7.26-1+deb9u1
  • every version up to 1.7.26-1+deb9u2: fixed in 1.7.26-1+deb9u2
—
ruby2.32.3.3-1, 2.3.3-1+deb9u1, 2.3.3-1+deb9u2
  • every version up to 2.3.3-1+deb9u3: fixed in 2.3.3-1+deb9u3
—
Alpine:v3.10(1)
PackageVulnerable rangeFix by version rangeDependents
ruby—
  • 2.2.0 up to 2.5.1-r0: fixed in 2.5.1-r0
—
Alpine:v3.11(1)
PackageVulnerable rangeFix by version rangeDependents
ruby—
  • 2.2.0 up to 2.5.1-r0: fixed in 2.5.1-r0
—
Alpine:v3.12(1)
PackageVulnerable rangeFix by version rangeDependents
ruby—
  • 2.2.0 up to 2.5.1-r0: fixed in 2.5.1-r0
—
Alpine:v3.13(1)
PackageVulnerable rangeFix by version rangeDependents
ruby—
  • 2.2.0 up to 2.5.1-r0: fixed in 2.5.1-r0
—
Alpine:v3.14(1)
PackageVulnerable rangeFix by version rangeDependents
ruby—
  • 2.2.0 up to 2.5.1-r0: fixed in 2.5.1-r0
—
Alpine:v3.15(1)
PackageVulnerable rangeFix by version rangeDependents
ruby—
  • 2.2.0 up to 2.5.1-r0: fixed in 2.5.1-r0
—
Alpine:v3.16(1)
PackageVulnerable rangeFix by version rangeDependents
ruby—
  • 2.2.0 up to 2.5.1-r0: fixed in 2.5.1-r0
—
Alpine:v3.17(1)
PackageVulnerable rangeFix by version rangeDependents
ruby—
  • 2.2.0 up to 2.5.1-r0: fixed in 2.5.1-r0
—
Alpine:v3.18(1)
PackageVulnerable rangeFix by version rangeDependents
ruby—
  • 2.2.0 up to 2.5.1-r0: fixed in 2.5.1-r0
—
Alpine:v3.19(1)
PackageVulnerable rangeFix by version rangeDependents
ruby—
  • 2.2.0 up to 2.5.1-r0: fixed in 2.5.1-r0
—
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
ruby—
  • 2.2.0 up to 2.5.1-r0: fixed in 2.5.1-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
ruby—
  • 2.2.0 up to 2.5.1-r0: fixed in 2.5.1-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
ruby—
  • 2.2.0 up to 2.5.1-r0: fixed in 2.5.1-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
ruby—
  • 2.2.0 up to 2.5.1-r0: fixed in 2.5.1-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
ruby—
  • 2.2.0 up to 2.5.1-r0: fixed in 2.5.1-r0
—
Alpine:v3.4(1)
PackageVulnerable rangeFix by version rangeDependents
ruby—
  • 2.2.0 up to 2.3.7-r0: fixed in 2.3.7-r0
—
Alpine:v3.5(1)
PackageVulnerable rangeFix by version rangeDependents
ruby—
  • 2.2.0 up to 2.3.7-r0: fixed in 2.3.7-r0
—
Alpine:v3.6(1)
PackageVulnerable rangeFix by version rangeDependents
ruby—
  • 2.2.0 up to 2.4.4-r0: fixed in 2.4.4-r0
—
Alpine:v3.7(1)
PackageVulnerable rangeFix by version rangeDependents
ruby—
  • 2.2.0 up to 2.4.4-r0: fixed in 2.4.4-r0
—
Alpine:v3.8(1)
PackageVulnerable rangeFix by version rangeDependents
ruby—
  • 2.2.0 up to 2.5.1-r0: fixed in 2.5.1-r0
—
Alpine:v3.9(1)
PackageVulnerable rangeFix by version rangeDependents
ruby—
  • 2.2.0 up to 2.5.1-r0: fixed in 2.5.1-r0
—
Debian:10(1)
PackageVulnerable rangeFix by version rangeDependents
jruby9.1.17.0-3
  • every version up to 9.1.17.0-3+deb10u1: fixed in 9.1.17.0-3+deb10u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
jruby—
  • every version up to 9.3.9.0+ds-1: fixed in 9.3.9.0+ds-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
jruby—
  • every version up to 9.3.9.0+ds-1: fixed in 9.3.9.0+ds-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
jruby—
  • every version up to 9.3.9.0+ds-1: fixed in 9.3.9.0+ds-1
—

Weakness Classification(1)

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

All Vendor Advisories

(8)

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 7× in last 7d / 21× 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.

Showing the most recent 100 of 145 total refreshes for this CVE.

  1. 2026-10-09 20:02 UTCEPSS rescore
  2. 2026-10-09 05:58 UTCOSV refresh
  3. 2026-10-08 16:36 UTCEPSS rescore
  4. 2026-10-07 23:41 UTCEPSS rescore
  5. 2026-10-06 15:12 UTCEPSS rescore
  6. 2026-10-05 17:38 UTCEPSS rescore
  7. 2026-10-03 14:21 UTCEPSS rescore
  8. 2026-09-30 14:59 UTCEPSS rescore
  9. 2026-09-30 09:30 UTCEG score recompute
  10. 2026-09-28 13:45 UTCEPSS rescore
  11. 2026-09-27 13:40 UTCEPSS rescore
  12. 2026-09-27 13:40 UTCEPSS rescore
  13. 2026-09-26 15:53 UTCEPSS rescore
  14. 2026-09-24 13:59 UTCEPSS rescore
  15. 2026-09-19 13:02 UTCOSV refresh
  16. 2026-09-18 19:22 UTCEPSS rescore
  17. 2026-09-17 19:22 UTCEPSS rescore
  18. 2026-09-15 03:05 UTCEPSS rescore
  19. 2026-09-15 03:05 UTCEPSS rescore
  20. 2026-09-12 14:55 UTCEPSS rescore
  21. 2026-09-11 09:31 UTCEPSS rescore
  22. 2026-09-07 15:56 UTCEPSS rescore
  23. 2026-09-06 13:43 UTCEPSS rescore
  24. 2026-09-05 15:23 UTCEPSS rescore
  25. 2026-09-04 13:56 UTCEPSS rescore
Show 75 more
  1. 2026-09-02 14:07 UTCEPSS rescore
  2. 2026-09-02 14:07 UTCEPSS rescore
  3. 2026-09-01 03:31 UTCEPSS rescore
  4. 2026-08-31 16:34 UTCOSV refresh
  5. 2026-08-30 19:13 UTCEPSS rescore
  6. 2026-08-27 14:21 UTCEPSS rescore
  7. 2026-08-26 14:41 UTCEPSS rescore
  8. 2026-08-25 13:44 UTCEPSS rescore
  9. 2026-08-21 23:44 UTCEPSS rescore
  10. 2026-08-20 22:51 UTCEPSS rescore
  11. 2026-08-19 16:59 UTCEPSS rescore
  12. 2026-08-18 13:43 UTCEPSS rescore
  13. 2026-08-16 14:51 UTCEPSS rescore
  14. 2026-08-16 02:10 UTCEPSS rescore
  15. 2026-08-15 01:26 UTCEPSS rescore
  16. 2026-08-14 21:24 UTCOSV refresh
  17. 2026-08-12 13:46 UTCEPSS rescore
  18. 2026-08-09 13:42 UTCEPSS rescore
  19. 2026-08-07 16:22 UTCEPSS rescore
  20. 2026-08-06 13:42 UTCEPSS rescore
  21. 2026-08-05 19:12 UTCEPSS rescore
  22. 2026-08-04 15:05 UTCEPSS rescore
  23. 2026-08-02 02:23 UTCEPSS rescore
  24. 2026-08-01 04:11 UTCEPSS rescore
  25. 2026-07-30 16:24 UTCEPSS rescore
  26. 2026-07-30 09:44 UTCOSV refresh
  27. 2026-07-30 01:26 UTCEPSS rescore
  28. 2026-07-28 15:32 UTCEPSS rescore
  29. 2026-07-26 14:51 UTCEPSS rescore
  30. 2026-07-23 14:15 UTCEPSS rescore
  31. 2026-07-23 01:28 UTCEG score recompute
  32. 2026-07-22 22:07 UTCEG score recompute
  33. 2026-07-22 14:04 UTCEPSS rescore
  34. 2026-07-22 14:04 UTCEPSS rescore
  35. 2026-07-21 15:21 UTCEPSS rescore
  36. 2026-07-21 15:21 UTCEPSS rescore
  37. 2026-07-20 17:04 UTCEPSS rescore
  38. 2026-07-19 14:28 UTCEPSS rescore
  39. 2026-07-19 14:28 UTCEPSS rescore
  40. 2026-07-19 02:26 UTCEPSS rescore
  41. 2026-07-19 02:26 UTCEPSS rescore
  42. 2026-07-18 10:00 UTCEPSS rescore
  43. 2026-07-16 16:59 UTCEPSS rescore
  44. 2026-07-16 16:59 UTCEPSS rescore
  45. 2026-07-15 16:54 UTCEPSS rescore
  46. 2026-07-15 01:56 UTCEPSS rescore
  47. 2026-07-15 01:56 UTCEPSS rescore
  48. 2026-07-13 22:26 UTCEPSS rescore
  49. 2026-07-12 19:07 UTCOSV refresh
  50. 2026-07-12 05:43 UTCEPSS rescore
  51. 2026-07-11 08:24 UTCEPSS rescore
  52. 2026-07-09 19:06 UTCEPSS rescore
  53. 2026-07-08 15:10 UTCEPSS rescore
  54. 2026-07-06 16:24 UTCEPSS rescore
  55. 2026-07-06 16:24 UTCEPSS rescore
  56. 2026-07-06 02:20 UTCEPSS rescore
  57. 2026-07-06 02:20 UTCEPSS rescore
  58. 2026-07-05 02:27 UTCEPSS rescore
  59. 2026-07-04 06:28 UTCEPSS rescore
  60. 2026-07-02 16:54 UTCEPSS rescore
  61. 2026-07-01 15:02 UTCEPSS rescore
  62. 2026-06-30 23:19 UTCEPSS rescore
  63. 2026-06-30 23:19 UTCEPSS rescore
  64. 2026-06-28 14:04 UTCEPSS rescore
  65. 2026-06-28 04:53 UTCEPSS rescore
  66. 2026-06-27 03:06 UTCEPSS rescore
  67. 2026-06-27 03:05 UTCEPSS rescore
  68. 2026-06-25 13:47 UTCEPSS rescore
  69. 2026-06-24 14:02 UTCEPSS rescore
  70. 2026-06-24 14:02 UTCEPSS rescore
  71. 2026-06-24 03:29 UTCOSV refresh
  72. 2026-06-23 21:30 UTCEPSS rescore
  73. 2026-06-22 14:23 UTCEPSS rescore
  74. 2026-06-22 14:23 UTCEPSS rescore
  75. 2026-06-21 14:54 UTCEPSS rescore

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2017-17742?
CVE-2017-17742 is a medium vulnerability published on April 3, 2018. Ruby before 2.2.10, 2.3.x before 2.3.7, 2.4.x before 2.4.4, 2.5.x before 2.5.1, and 2.6.0-preview1 allows an HTTP Response Splitting attack. An attacker can inject a crafted key and value into an HTTP response for the HTTP server of WEBrick.
When was CVE-2017-17742 disclosed?
CVE-2017-17742 was first published on April 3, 2018, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-17742 actively exploited?
CVE-2017-17742 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 5.5% probability of exploitation in the next 30 days (92nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2017-17742?
CVE-2017-17742 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2017-17742?
A fix for CVE-2017-17742 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-17742

Explore →

Is Your Infrastructure Affected by CVE-2017-17742?

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

Book a Demo →Browse All CVEs