https-proxy-agent up to 2.1.0 on Node.js JSON auth memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.9 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as problematic has been discovered in https-proxy-agent up to 2.1.0 on Node.js. Affected by this vulnerability is an unknown functionality of the component JSON Handler. Executing a manipulation of the argument auth as part of Parameter can lead to memory corruption. This vulnerability appears as CVE-2018-3739. The attack may be performed from remote. There is no available exploit. It is advisable to upgrade the affected component.
Details
A vulnerability has been found in https-proxy-agent up to 2.1.0 on Node.js (Firewall Software) and classified as problematic. This vulnerability affects an unknown functionality of the component JSON Handler. The manipulation of the argument auth as part of a Parameter leads to a memory corruption vulnerability. The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. As an impact it is known to affect availability. CVE summarizes:
https-proxy-agent before 2.1.1 passes auth option to the Buffer constructor without proper sanitization, resulting in DoS and uninitialized memory leak in setups where an attacker could submit typed input to the 'auth' parameter (e.g. JSON).
The bug was discovered 04/24/2018. The weakness was presented 06/07/2018 (Website). The advisory is available at hackerone.com. This vulnerability was named CVE-2018-3739 since 12/28/2017. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Technical details are known, but there is no available exploit.
The vulnerability was handled as a non-public zero-day exploit for at least 43 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 2.1.1 eliminates this vulnerability.
See VDB-119215 for similar entry. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.2VulDB Meta Temp Score: 7.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.1
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: Memory corruptionCWE: CWE-119
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: https-proxy-agent 2.1.1
Timeline
12/28/2017 🔍04/24/2018 🔍
06/06/2018 🔍
06/07/2018 🔍
06/08/2018 🔍
02/17/2020 🔍
Sources
Advisory: hackerone.comStatus: Not defined
CVE: CVE-2018-3739 (🔍)
GCVE (CVE): GCVE-0-2018-3739
GCVE (VulDB): GCVE-100-119218
See also: 🔍
Entry
Created: 06/08/2018 08:45Updated: 02/17/2020 08:12
Changes: 06/08/2018 08:45 (62), 02/17/2020 08:12 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.