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.
Metrics
Affected Vendors & Products
Advisories
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2018-0210 | 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. |
Github GHSA |
GHSA-2xvj-j3qh-x8c3 | private_address_check contains race condition |
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
No history.
Status: PUBLISHED
Assigner: hackerone
Published:
Updated: 2024-09-16T20:26:38.707Z
Reserved: 2017-12-28T00:00:00
Link: CVE-2018-3759
No data.
Status : Modified
Published: 2018-06-13T15:29:00.267
Modified: 2024-11-21T04:06:01.377
Link: CVE-2018-3759
No data.
OpenCVE Enrichment
No data.
EUVD
Github GHSA