CVE-2018-3759

Description

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

Category

3.7
CVSS
Severity: Low
CVSS 3.0 •
CVSS 2.0 •
EPSS 0.18%
Third-Party Advisory github.com
Affected: HackerOne private_address_check ruby gem
Published at:
Updated at:

References

Link Tags
https://github.com/jtdowney/private_address_check/commit/4068228187db87fea7577f7020099399772bb147 third party advisory patch

Frequently Asked Questions

What is the severity of CVE-2018-3759?
CVE-2018-3759 has been scored as a low severity vulnerability.
How to fix CVE-2018-3759?
To fix CVE-2018-3759, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2018-3759 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2018-3759 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2018-3759?
CVE-2018-3759 affects HackerOne private_address_check ruby gem.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.