The Private Address Check Project maintains a utility library for validating private and reserved IP address ranges, a modestly represented component in network security tooling. Its disclosures cluster around concurrency and exception-handling issues, including race conditions, improper handling of edge cases, and incomplete input filtering, reflecting the synchronization and parsing demands of address-validation logic. Treat this as a compact vendor profile; live severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Private Address Check Project over time
Signals from CVEs in this vendor scope (3 CVEs).
3 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2017-0909CRITICAL 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 reque | Nov 16, 2017 | 9.8 | 24 | NO | NO |
CVE-2017-0904HIGH 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 s | Nov 13, 2017 | 8.1 | 23 | NO | NO |
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 w | Jun 13, 2018 | 3.7 | 17 | NO | NO |
Signals from CVEs in this vendor scope (3 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Private Address Check Project.
Media articles that mention a CVE ID that affects a product developed by Private Address Check Project — matched by CVE ID, not by vendor name.