CVE-2017-0904 json
private_address_check vulnerable to bypass of Resolv.getaddresses method
published 2017-11-13 8 y ago modified 2026-06-17 4 mo ago also GHSA-hxhj-hp9m-qwc4 , EUVD-2017-0348
- cvss
- 8.1
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.4%
- EPSS 2.4% chance of exploitation in 30 days, percentile 84%
- public exploits
- 0
- none known
Summary
The private_address_check ruby gem before 0.4.0 is vulnerable to a bypass due to use of Ruby's Resolv.getaddresses method, which is OS-dependent and should not be relied upon for security measures, such as when used to blacklist private network addresses to prevent server-side request forgery.
Patch / fix
- rubygems private_address_check 0.4.0
- private_address_check_project private_address_check 0.4.0
Exploit prediction
2.42% chance of exploitation in the next 30 days, higher than 84% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 8.1 | CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| rubygems | private_address_check | <0.4.0 |
0.4.0 |
Affected products
- jtdowney private_address_check ruby gem
Classification
References
-
github.com
/jtdowney/private_address_check/commit/58a0d7fe31de339c0117160567a5b33ad82b46af
web, third-party-advisory
-
hackerone.com
/reports/287245
web, issue-tracking, mitigation, patch, third-party-advisory
-
edoverflow.com
/2017/ruby-resolv-bug/
issue-tracking, third-party-advisory
-
github.com
/jtdowney/private_address_check/issues/1
web, issue-tracking, third-party-advisory
-
hackerone.com
/reports/287835
web, permissions-required, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2017-0904
advisory
-
edoverflow.com
/2017/ruby-resolv-bug
web
Sources
- CVE List CVE-2017-0904
- GitHub Advisory GHSA-hxhj-hp9m-qwc4
- NVD CVE-2017-0904
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.