private_address_check Ruby Gem up to 0.4.x on Ruby Socket race condition
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.6 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic was found in private_address_check Ruby Gem up to 0.4.x on Ruby. The affected element is an unknown function of the component Socket Handler. The manipulation results in race condition. This vulnerability is reported as CVE-2018-3759. The attack can be launched remotely. No exploit exists. Upgrading the affected component is advised.
Details
A vulnerability, which was classified as problematic, was found in private_address_check Ruby Gem up to 0.4.x on Ruby (Ruby Gem). Affected is an unknown function of the component Socket Handler. The manipulation with an unknown input leads to a race condition vulnerability. CWE is classifying the issue as CWE-362. The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently. This is going to have an impact on confidentiality. CVE summarizes:
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.
The bug was discovered 05/04/2018. The weakness was disclosed 06/13/2018 (Website). The advisory is shared for download at github.com. This vulnerability is traded as CVE-2018-3759 since 12/28/2017. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. There are neither technical details nor an exploit publicly available.
The vulnerability was handled as a non-public zero-day exploit for at least 40 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 0.5.0 eliminates this vulnerability.
Once again VulDB remains the best source for vulnerability data.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.7VulDB Meta Temp Score: 3.7
VulDB Base Score: 3.7
VulDB Temp Score: 3.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 3.7
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Race conditionCWE: CWE-362
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: private_address_check Ruby Gem 0.5.0
Patch: github.com
Timeline
12/28/2017 🔍05/04/2018 🔍
06/13/2018 🔍
06/13/2018 🔍
06/14/2018 🔍
03/27/2023 🔍
Sources
Advisory: 4068228187db87fea7577f7020099399772bb147Status: Not defined
CVE: CVE-2018-3759 (🔍)
GCVE (CVE): GCVE-0-2018-3759
GCVE (VulDB): GCVE-100-119532
Entry
Created: 06/14/2018 10:23Updated: 03/27/2023 11:44
Changes: 06/14/2018 10:23 (59), 02/19/2020 11:12 (1), 03/27/2023 11:44 (4)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.