Low severity · published Jun 13, 2018
CVE-2018-3759
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
3.7
CVSS
0.7%
EPSS
No
On KEV
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.
CVSS vector
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Confidentiality
Low
Integrity
None
Availability
None
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.7% · higher than 52% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
PA
Private Address Check · Private Address Check Project
before 0.5.0 · source: NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2018-3759
CVE.org
https://www.cve.org/CVERecord?id=CVE-2018-3759
Patch
https://github.com/jtdowney/private_address_check/commit/4068228187db87fea7577f7020099399772bb147
More from Private Address Check
9.8
CVE-2017-0909
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…
8.1
CVE-2017-0904
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…