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.
CVE-2017-17790
Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-05-14. NVD baseline CVSS 9.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 9.8
- EG Score
- 9.8(medium)
- EG Risk
- 51(Track)EG Risk 51/100SSVC: Track
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 computedSeverity98% × 45%Exploitation6% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 6%
- EPSS %ILE
- 93%
- KEV
- Not listed
Published
December 20, 2017
Last Modified
June 17, 2026
Advisory Details (9)
Auto-updated Aug 25, 2026Affected: Red Hat Enterprise Linux 7.
https://access.redhat.com/errata/RHSA-2018:0378[SECURITY] [DLA 1421-1] ruby2.1 security update
https://lists.debian.org/debian-lts-announce/2018/07/msg00012.html[SECURITY] [DLA 1221-1] ruby1.9.1 security update
https://lists.debian.org/debian-lts-announce/2017/12/msg00025.html[SECURITY] [DLA 1222-1] ruby1.8 security update
https://lists.debian.org/debian-lts-announce/2017/12/msg00024.htmlFixed command Injection
Upstream fix in progress (PR #1777 · ruby/ruby, state=closed)
https://github.com/ruby/ruby/pull/1777Patch Availability(5)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | ruby2.3-tcltk (2.3.1-2~16.04.5) @ xenial | 2026-05-20 | ubuntu |
| redhat | rh-ruby24-ruby-0:2.4.3-90.el7 | 2018-03-26 | redhat |
| redhat | rh-ruby23-ruby-0:2.3.6-67.el7 | 2018-03-26 | redhat |
| redhat | rh-ruby22-ruby-0:2.2.9-19.el7 | 2018-03-26 | redhat |
| redhat | ruby-0:2.0.0.648-33.el7_4 | 2018-02-28 | redhat |
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
(4 across 3 ecosystems)
Debian:7(2)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| ruby1.8 | 1.8.7.358-7 ... 1.8.7.358-7.1+deb7u4 (6 versions) | 1.8.7.358-7.1+deb7u5 | — |
| ruby1.9.1 | 1.9.3.194-8.1 ... 1.9.3.194-8.1+deb7u6 (6 versions) | 1.9.3.194-8.1+deb7u7 | — |
Debian:8(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| ruby2.1 | 2.1.5-2, 2.1.5-2+deb8u1, 2.1.5-2+deb8u2, 2.1.5-2+deb8u3 | 2.1.5-2+deb8u4 | — |
Debian:9(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| ruby2.3 | 2.3.3-1, 2.3.3-1+deb9u1, 2.3.3-1+deb9u2 | 2.3.3-1+deb9u3 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
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 5× in last 7d / 22× 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 140 total refreshes for this CVE.
- 2026-08-27 01:30 UTCOSV refresh
- 2026-08-26 14:41 UTCEPSS rescore
- 2026-08-25 13:44 UTCEPSS rescore
- 2026-08-21 23:44 UTCEPSS rescore
- 2026-08-20 22:51 UTCEPSS rescore
- 2026-08-19 16:59 UTCEPSS rescore
- 2026-08-18 13:43 UTCEPSS rescore
- 2026-08-16 14:51 UTCEPSS rescore
- 2026-08-16 02:10 UTCEPSS rescore
- 2026-08-15 01:26 UTCEPSS rescore
- 2026-08-12 13:46 UTCEPSS rescore
- 2026-08-10 15:08 UTCOSV refresh
- 2026-08-09 13:42 UTCEPSS rescore
- 2026-08-07 16:22 UTCEPSS rescore
- 2026-08-06 13:42 UTCEPSS rescore
- 2026-08-05 19:12 UTCEPSS rescore
- 2026-08-04 15:05 UTCEPSS rescore
- 2026-08-02 02:23 UTCEPSS rescore
- 2026-08-01 04:11 UTCEPSS rescore
- 2026-07-30 16:24 UTCEPSS rescore
- 2026-07-30 01:26 UTCEPSS rescore
- 2026-07-28 15:32 UTCEPSS rescore
- 2026-07-26 14:51 UTCEPSS rescore
- 2026-07-25 16:00 UTCOSV refresh
- 2026-07-23 14:15 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-07-23 01:28 UTCEG score recompute
- 2026-07-22 22:07 UTCEG score recompute
- 2026-07-22 14:04 UTCEPSS rescore
- 2026-07-22 14:04 UTCEPSS rescore
- 2026-07-21 15:21 UTCEPSS rescore
- 2026-07-21 15:21 UTCEPSS rescore
- 2026-07-20 17:04 UTCEPSS rescore
- 2026-07-19 14:28 UTCEPSS rescore
- 2026-07-19 14:28 UTCEPSS rescore
- 2026-07-19 02:26 UTCEPSS rescore
- 2026-07-19 02:26 UTCEPSS rescore
- 2026-07-18 10:00 UTCEPSS rescore
- 2026-07-16 16:59 UTCEPSS rescore
- 2026-07-16 16:59 UTCEPSS rescore
- 2026-07-15 16:54 UTCEPSS rescore
- 2026-07-15 01:56 UTCEPSS rescore
- 2026-07-15 01:56 UTCEPSS rescore
- 2026-07-13 22:26 UTCEPSS rescore
- 2026-07-12 05:43 UTCEPSS rescore
- 2026-07-11 08:24 UTCEPSS rescore
- 2026-07-09 19:06 UTCEPSS rescore
- 2026-07-08 15:10 UTCEPSS rescore
- 2026-07-08 10:57 UTCOSV refresh
- 2026-07-07 13:42 UTCEPSS rescore
- 2026-07-06 16:24 UTCEPSS rescore
- 2026-07-06 16:24 UTCEPSS rescore
- 2026-07-06 02:20 UTCEPSS rescore
- 2026-07-06 02:20 UTCEPSS rescore
- 2026-07-05 02:27 UTCEPSS rescore
- 2026-07-04 06:28 UTCEPSS rescore
- 2026-07-02 16:54 UTCEPSS rescore
- 2026-07-01 15:02 UTCEPSS rescore
- 2026-06-30 23:19 UTCEPSS rescore
- 2026-06-30 23:19 UTCEPSS rescore
- 2026-06-28 14:04 UTCEPSS rescore
- 2026-06-28 04:53 UTCEPSS rescore
- 2026-06-27 03:06 UTCEPSS rescore
- 2026-06-27 03:05 UTCEPSS rescore
- 2026-06-25 13:47 UTCEPSS rescore
- 2026-06-24 14:02 UTCEPSS rescore
- 2026-06-24 14:02 UTCEPSS rescore
- 2026-06-23 21:30 UTCEPSS rescore
- 2026-06-22 14:23 UTCEPSS rescore
- 2026-06-22 14:23 UTCEPSS rescore
- 2026-06-21 14:54 UTCEPSS rescore
- 2026-06-21 14:54 UTCEPSS rescore
- 2026-06-21 01:57 UTCEPSS rescore
- 2026-06-21 01:57 UTCEPSS rescore
- 2026-06-19 22:53 UTCOSV refresh
- 2026-06-19 19:23 UTCEPSS rescore
- 2026-06-19 19:23 UTCEPSS rescore
- 2026-06-18 17:50 UTCEPSS rescore
- 2026-06-17 17:50 UTCEPSS rescore
- 2026-06-16 17:50 UTCEPSS rescore
- 2026-06-16 17:50 UTCEPSS rescore
- 2026-06-15 17:45 UTCEPSS rescore
- 2026-06-14 23:14 UTCEPSS rescore
- 2026-06-13 22:57 UTCEPSS rescore
- 2026-06-12 23:09 UTCEPSS rescore
- 2026-06-10 22:15 UTCEPSS rescore
- 2026-06-10 13:19 UTCEPSS rescore
- 2026-06-08 14:14 UTCEPSS rescore
- 2026-06-08 14:14 UTCEPSS rescore
- 2026-06-07 15:22 UTCEPSS rescore
- 2026-06-07 15:22 UTCEPSS rescore
- 2026-06-06 13:45 UTCEPSS rescore
- 2026-06-06 13:45 UTCEPSS rescore
- 2026-06-05 22:44 UTCEPSS rescore
- 2026-06-05 06:08 UTCEPSS rescore
- 2026-06-05 06:08 UTCEPSS rescore
- 2026-06-04 13:10 UTCEPSS rescore
- 2026-06-02 20:11 UTCEPSS rescore
- 2026-06-02 20:11 UTCEPSS rescore
- 2026-06-01 13:49 UTCEPSS rescore
- 2026-05-31 22:28 UTCEPSS rescore
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat
- CVE-2001-0825EG 10.0HIGH
- CVE-2001-1009EG 10.0EPSS p93HIGH
- CVE-2001-0554EG 10.0EPSS p98HIGH
- CVE-2001-1162EG 10.0EPSS p96HIGH
- CVE-2001-0414EG 10.0EPSS p100HIGH
- CVE-2001-0191EG 10.0EPSS p92HIGH
- CVE-2001-0301EG 10.0EPSS p91HIGH
- CVE-2001-0197EG 10.0EPSS p96HIGH
- CVE-2001-0233EG 10.0EPSS p96HIGH
- CVE-2001-0010EG 10.0EPSS p98HIGH
Same CWE
10 shownCWE-74
- CVE-2014-8423EG 10.0EPSS p99HIGH
- CVE-2015-10062NVD 5.5EG 9.8CRITICAL
- CVE-2015-10027NVD 5.5EG 9.8CRITICAL
- CVE-2016-15007NVD 5.5EG 9.8CRITICAL
- CVE-2016-15004NVD 7.3EG 9.8CRITICAL
- CVE-2013-4144EG 9.8CRITICAL
- CVE-2013-7487EG 9.8CRITICAL
- CVE-2014-4678EG 9.8EPSS p92CRITICAL
- CVE-2014-4967EG 9.8CRITICAL
- CVE-2014-4966EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2017-17790?
When was CVE-2017-17790 disclosed?
Is CVE-2017-17790 actively exploited?
What is the CVSS score of CVE-2017-17790?
How do I remediate CVE-2017-17790?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2017-17790
Is Your Infrastructure Affected by CVE-2017-17790?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.