Skip to content
Fencer Intel
critical 9.8

CVE-2017-0909 json

private_address_check contains Incomplete List of Disallowed Inputs

published 2017-11-16 8 y ago modified 2026-06-17 4 mo ago also GHSA-3v3c-r5v2-68ph , EUVD-2017-0339

cvss
9.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.0%
EPSS 2.0% chance of exploitation in 30 days, percentile 81%
public exploits
0
none known

Summary

The private_address_check ruby gem before 0.4.1 is vulnerable to a bypass due to an incomplete blacklist of common private/local network addresses used to prevent server-side request forgery.

Patch / fix

  • rubygems private_address_check 0.4.1
  • private_address_check_project private_address_check 0.4.1

Exploit prediction

2.03% chance of exploitation in the next 30 days, higher than 81% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Affected packages

ecosystem package affected fixed in
rubygems private_address_check
<0.4.1
0.4.1

Affected products

  • HackerOne private_address_check ruby gem

Classification

Weakness
  • CWE-184 Incomplete List of Disallowed Inputs

References

Sources

Fencer Intel 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.