| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.9 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in ljharb npm-lockfile. Affected by this vulnerability is an unknown functionality. This manipulation causes os command injection. This vulnerability is handled as CVE-2022-0841. The attack can only be done within the local network. There is not any exploit available. You should upgrade the affected component.
Details
A vulnerability has been found in ljharb npm-lockfile (Software Library) and classified as critical. Affected by this vulnerability is some unknown functionality. The manipulation with an unknown input leads to a os command injection vulnerability. The CWE definition for the vulnerability is CWE-78. The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component. As an impact it is known to affect confidentiality, integrity, and availability.
The weakness was released 03/03/2022. The advisory is shared at huntr.dev. This vulnerability is known as CVE-2022-0841 since 03/03/2022. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1202 for this issue.
Upgrading to version 2.0.5 eliminates this vulnerability. Applying the patch bfdb84813260f0edbf759f2fde1e8c816c1478b8 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.1VulDB Meta Temp Score: 4.9
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 3.8
CNA Vector (huntr.dev): 🔍
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
Class: Os command injectionCWE: CWE-78 / CWE-77 / CWE-74
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
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: npm-lockfile 2.0.5
Patch: bfdb84813260f0edbf759f2fde1e8c816c1478b8
Timeline
03/03/2022 🔍03/03/2022 🔍
03/03/2022 🔍
03/06/2022 🔍
Sources
Product: github.comAdvisory: bfdb84813260f0edbf759f2fde1e8c816c1478b8
Status: Confirmed
CVE: CVE-2022-0841 (🔍)
GCVE (CVE): GCVE-0-2022-0841
GCVE (VulDB): GCVE-100-194161
Entry
Created: 03/03/2022 20:56Updated: 03/06/2022 09:31
Changes: 03/03/2022 20:56 (50), 03/06/2022 09:31 (2)
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.