CVE-2017-17790

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

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, ghsa, nvd
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 6%CVSS: 9.8Exploit: NoneExposed: 0

A fix is available — apply it.

The lazy_initialize function in lib/resolv.rb in Ruby through 2.4.3 uses Kernel#open, which might allow Command Injection attacks, as demonstrated by a Resolv::Hosts::new argument beginning with a '|' character, a different vulnerability than CVE-2017-17405. NOTE: situations with untrusted input may be highly unlikely.

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
92.4%
KEV
Not listed

Published

December 20, 2017

Last Modified

May 13, 2026

Advisory Details (9)

Auto-updated Jun 21, 2026
Patch available. Sources: redhat, github_pr.
redhat Patch Available

Affected: Red Hat Enterprise Linux 7.

https://access.redhat.com/errata/RHSA-2018:0378
generic

[SECURITY] [DSA 4259-1] ruby2.3 security update

https://www.debian.org/security/2018/dsa-4259
generic Patch Available

[SECURITY] [DLA 1421-1] ruby2.1 security update

https://lists.debian.org/debian-lts-announce/2018/07/msg00012.html
generic Patch Available

[SECURITY] [DLA 1221-1] ruby1.9.1 security update

https://lists.debian.org/debian-lts-announce/2017/12/msg00025.html
generic Patch Available

[SECURITY] [DLA 1222-1] ruby1.8 security update

https://lists.debian.org/debian-lts-announce/2017/12/msg00024.html
github_pr

Fixed command Injection

Upstream fix in progress (PR #1777 · ruby/ruby, state=closed)

https://github.com/ruby/ruby/pull/1777
redhat Patch Available
https://access.redhat.com/errata/RHSA-2018:0585
redhat Patch Available
https://access.redhat.com/errata/RHSA-2018:0584
redhat Patch Available
https://access.redhat.com/errata/RHSA-2018:0583

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
ubunturuby2.3-tcltk (2.3.1-2~16.04.5) @ xenial2026-05-20ubuntu
redhatrh-ruby24-ruby-0:2.4.3-90.el72018-03-26redhat
redhatrh-ruby23-ruby-0:2.3.6-67.el72018-03-26redhat
redhatrh-ruby22-ruby-0:2.2.9-19.el72018-03-26redhat
redhatruby-0:2.0.0.648-33.el7_42018-02-28redhat

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

(5)

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 11× in last 7d / 40× 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 101 total refreshes for this CVE.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2017-17790?
CVE-2017-17790 is a critical vulnerability published on December 20, 2017. The lazy_initialize function in lib/resolv.rb in Ruby through 2.4.3 uses Kernel#open, which might allow Command Injection attacks, as demonstrated by a Resolv::Hosts::new argument beginning with a '|' character, a different vulnerability than CVE-2017-17405. NOTE: situations with untrusted input…
When was CVE-2017-17790 disclosed?
CVE-2017-17790 was first published in the National Vulnerability Database on December 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-17790 actively exploited?
CVE-2017-17790 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 92.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2017-17790?
CVE-2017-17790 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2017-17790?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-17790, 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-17790

Explore →

Is Your Infrastructure Affected by CVE-2017-17790?

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

Start Free Scan →Browse All CVEs