{"api_version":"1","generated_at":"2026-07-23T10:16:27+00:00","cve":"CVE-2018-3759","urls":{"html":"https://cve.report/CVE-2018-3759","api":"https://cve.report/api/cve/CVE-2018-3759.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2018-3759","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2018-3759"},"summary":{"title":"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.","state":"PUBLIC","assigner":"support@hackerone.com","published_at":"2018-06-13 15:29:00","updated_at":"2019-10-09 23:40:00"},"problem_types":["CWE-362"],"metrics":[],"references":[{"url":"https://github.com/jtdowney/private_address_check/commit/4068228187db87fea7577f7020099399772bb147","name":"https://github.com/jtdowney/private_address_check/commit/4068228187db87fea7577f7020099399772bb147","refsource":"MISC","tags":["Patch","Third Party Advisory"],"title":"Fix TOCTOU bug · jtdowney/private_address_check@4068228 · GitHub","mime":"text/html","httpstatus":"200","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2018-3759","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2018-3759","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[{"cve_year":"2018","cve_id":"3759","vulnerable":"1","versionEndIncluding":"","cpe1":"cpe","cpe2":"2.3","cpe3":"a","cpe4":"private_address_check_project","cpe5":"private_address_check","cpe6":"*","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"*","cpe11":"ruby","cpe12":"*","cpe13":"*"},{"cve_year":"2018","cve_id":"3759","vulnerable":"1","versionEndIncluding":"1","cpe1":"cpe","cpe2":"2.3","cpe3":"a","cpe4":"private_address_check_project","cpe5":"private_address_check","cpe6":"*","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"*","cpe11":"ruby","cpe12":"*","cpe13":"*"}],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"CVE_data_meta":{"ASSIGNER":"support@hackerone.com","DATE_PUBLIC":"2018-05-03T00:00:00","ID":"CVE-2018-3759","STATE":"PUBLIC"},"affects":{"vendor":{"vendor_data":[{"product":{"product_data":[{"product_name":"private_address_check ruby gem","version":{"version_data":[{"version_value":"0.5.0"}]}}]},"vendor_name":"HackerOne"}]}},"data_format":"MITRE","data_type":"CVE","data_version":"4.0","description":{"description_data":[{"lang":"eng","value":"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."}]},"problemtype":{"problemtype_data":[{"description":[{"lang":"eng","value":"Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') (CWE-362)"}]}]},"references":{"reference_data":[{"name":"https://github.com/jtdowney/private_address_check/commit/4068228187db87fea7577f7020099399772bb147","refsource":"MISC","url":"https://github.com/jtdowney/private_address_check/commit/4068228187db87fea7577f7020099399772bb147"}]}},"nvd":{"publishedDate":"2018-06-13 15:29:00","lastModifiedDate":"2019-10-09 23:40:00","problem_types":["CWE-362"],"metrics":{"baseMetricV3":{"cvssV3":{"version":"3.0","vectorString":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N","attackVector":"NETWORK","attackComplexity":"HIGH","privilegesRequired":"NONE","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"LOW","integrityImpact":"NONE","availabilityImpact":"NONE","baseScore":3.7,"baseSeverity":"LOW"},"exploitabilityScore":2.2,"impactScore":1.4},"baseMetricV2":{"cvssV2":{"version":"2.0","vectorString":"AV:N/AC:M/Au:N/C:P/I:N/A:N","accessVector":"NETWORK","accessComplexity":"MEDIUM","authentication":"NONE","confidentialityImpact":"PARTIAL","integrityImpact":"NONE","availabilityImpact":"NONE","baseScore":4.3},"severity":"MEDIUM","exploitabilityScore":8.6,"impactScore":2.9,"obtainAllPrivilege":false,"obtainUserPrivilege":false,"obtainOtherPrivilege":false,"userInteractionRequired":false}},"configurations":{"CVE_data_version":"4.0","nodes":[{"operator":"OR","children":[],"cpe_match":[{"vulnerable":true,"cpe23Uri":"cpe:2.3:a:private_address_check_project:private_address_check:*:*:*:*:*:ruby:*:*","versionEndExcluding":"0.5.0","cpe_name":[]}]}]}},"legacy_mitre":{"record":{"CveYear":"2018","CveId":"3759","Ordinal":"119586","Title":"CVE-2018-3759","CVE":"CVE-2018-3759","Year":"2018"},"notes":[{"CveYear":"2018","CveId":"3759","Ordinal":"1","NoteData":"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.","Type":"Description","Title":null},{"CveYear":"2018","CveId":"3759","Ordinal":"2","NoteData":"2018-06-13","Type":"Other","Title":"Published"},{"CveYear":"2018","CveId":"3759","Ordinal":"3","NoteData":"2018-06-13","Type":"Other","Title":"Modified"}]}}}