private_address_check ruby gem before 0.5.0 is vulnerable to a time-of-check time-of-use (TOCTOU) race condition due to the address the socket uses not being checked. DNS entries with a TTL of 0 can trigger this case where the initial resolution is a public address but the subseq...
Vendor
private address check project vulnerabilities
3 published CVES affecting private address check project, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 3
- Critical
- 1
- High
- 1
- Medium
- 0
- Low
- 1
- Unscored
- 0
- CISA KEV
- 0
Products
Latest private address check project CVEs
Newest publication first
-
LowCVSS 3.7 EPSS 0.68% PoC
-
CriticalCVSS 9.8 EPSS 2.0%
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.
-
HighCVSS 8.1 EPSS 2.4%
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 re...
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.