PatchTheCVEprivate address check vulnerabilities and fixes
Recent CVEs affecting private address check, with upgrade or downgrade steps. 3 tracked.
Also searched as: privateaddresscheck.
private address check has 3 tracked vulnerabilities, 1 critical. A fixed release or vendor patch exists for 3. Most recent: 2018-06-13. Highest priority: CVE-2017-0909 (score 60/100).
- CVE-2018-3759 LOW 3.7 UPGRADE private_address_check ruby gem before 0.5.0 is vulnerable to a time-of-check time-of-use (TOCTOU) race conditi
- CVE-2017-0909 CRITICAL 9.8 UPGRADE The private_address_check ruby gem before 0.4.1 is vulnerable to a bypass due to an incomplete blacklist of co
- CVE-2017-0904 HIGH 8.1 UPGRADE The private_address_check ruby gem before 0.4.0 is vulnerable to a bypass due to use of Ruby's Resolv.getaddre
FAQ
How do I fix private address check vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is private address check being exploited right now?
None of the tracked private address check CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which private address check CVE should I patch first?
CVE-2017-0909 currently ranks highest (60/100): The private_address_check ruby gem before 0.4.1 is vulnerable to a bypass due to an incomplete blacklist of co.