locutus Package on npm php.strings.parse_str Prototype privileges management
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in locutus Package on npm. It has been classified as critical. The affected element is the function php.strings.parse_str. The manipulation leads to privileges management (Prototype).
This vulnerability is traded as CVE-2020-7719. It is possible to initiate the attack remotely. There is no exploit available.
Details
A vulnerability was found in locutus Package on npm (unknown version) and classified as critical. This issue affects the function php.strings.parse_str. The manipulation with an unknown input leads to a privileges management vulnerability (Prototype). Using CWE to declare the problem leads to CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
All versions of package locutus are vulnerable to Prototype Pollution via the php.strings.parse_str function.
The weakness was shared 09/01/2020 (Website). The advisory is shared at snyk.io. The identification of this vulnerability is CVE-2020-7719 since 01/21/2020. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1068 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.5
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
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: 🔍
Exploiting
Name: PrototypeClass: Privileges management / Prototype
CWE: CWE-269 / CWE-266
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
01/21/2020 🔍09/01/2020 🔍
09/01/2020 🔍
11/12/2020 🔍
Sources
Advisory: snyk.ioStatus: Not defined
Confirmation: 🔍
CVE: CVE-2020-7719 (🔍)
GCVE (CVE): GCVE-0-2020-7719
GCVE (VulDB): GCVE-100-160529
Entry
Created: 09/01/2020 17:25Updated: 11/12/2020 08:52
Changes: 09/01/2020 17:25 (37), 09/01/2020 17:30 (11), 11/12/2020 08:49 (1), 11/12/2020 08:52 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.