private_address_check 0.2.0

3 security vulnerabilities found in version 0.2.0

private_address_check Ruby Gem Blacklist Bypass privilege escalation

critical severity CVE-2017-0909
critical severity CVE-2017-0909
Patched versions: >= 0.4.1

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.

private_address_check Ruby Gem Time-of-check Time-of-use race condition

high severity CVE-2018-3759
high severity CVE-2018-3759
Patched versions: >= 0.5.0

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 by the subsequent resolution is a private address.

private_address_check Ruby Gem Resolv.getaddresses Server-Side Request Forgery

high severity CVE-2017-0904
high severity CVE-2017-0904
Patched versions: >= 0.4.0

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.

No officially reported memory leakage issues detected.


This gem version does not have any officially reported memory leaked issues.

No license issues detected.


This gem version has a license in the gemspec.

This gem version is available.


This gem version has not been yanked and is still available for usage.