CVE-2021-37701 Security Vulnerability & Exploit Details

CVE-2021-37701
Vulnerability Scoring

8.2

/10

Severe Risk

Cybersecurity professionals consider CVE-2021-37701 an immediate threat requiring urgent mitigation.

Attack Complexity Details

Attack Complexity: Low
Exploits can be performed without significant complexity or special conditions.
Attack Vector: Local
Vulnerability requires local system access.
Privileges Required: None
No privileges are required for exploitation.
Scope: Changed
Successful exploitation can impact components beyond the vulnerable component.
User Interaction: Required
User interaction is necessary for successful exploitation.

CVE-2021-37701 Details

Status: Modified

Last updated: 🕕 21 Nov 2024, 06:15 UTC
Originally published on: 🕔 31 Aug 2021, 17:15 UTC

Time between publication and last update: 1177 days

CVSS Release: version 3

CVSS3 Source

security-advisories@github.com

CVSS3 Type

Secondary

CVSS3 Vector

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N

CVE-2021-37701 Vulnerability Summary

CVE-2021-37701: The npm package "tar" (aka node-tar) before versions 4.4.16, 5.0.8, and 6.1.7 has an arbitrary file creation/overwrite and arbitrary code execution vulnerability. node-tar aims to guarantee that any file whose location would be modified by a symbolic link is not extracted. This is, in part, achieved by ensuring that extracted directories are not symlinks. Additionally, in order to prevent unnecessary stat calls to determine whether a given path is a directory, paths are cached when directories are created. This logic was insufficient when extracting tar files that contained both a directory and a symlink with the same name as the directory, where the symlink and directory names in the archive entry used backslashes as a path separator on posix systems. The cache checking logic used both `\` and `/` characters as path separators, however `\` is a valid filename character on posix systems. By first creating a directory, and then replacing that directory with a symlink, it was thus possible to bypass node-tar symlink checks on directories, essentially allowing an untrusted tar file to symlink into an arbitrary location and subsequently extracting arbitrary files into that location, thus allowing arbitrary file creation and overwrite. Additionally, a similar confusion could arise on case-insensitive filesystems. If a tar archive contained a directory at `FOO`, followed by a symbolic link named `foo`, then on case-insensitive file systems, the creation of the symbolic link would remove the directory from the filesystem, but _not_ from the internal directory cache, as it would not be treated as a cache hit. A subsequent file entry within the `FOO` directory would then be placed in the target of the symbolic link, thinking that the directory had already been created. These issues were addressed in releases 4.4.16, 5.0.8 and 6.1.7. The v3 branch of node-tar has been deprecated and did not receive patches for these issues. If you are still using a v3 release we recommend you update to a more recent version of node-tar. If this is not possible, a workaround is available in the referenced GHSA-9r2w-394v-53qc.

Assessing the Risk of CVE-2021-37701

Access Complexity Graph

The exploitability of CVE-2021-37701 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2021-37701

With low attack complexity and no required privileges, CVE-2021-37701 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2021-37701, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2021-37701, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

Confidentiality: High
Exploiting CVE-2021-37701 can result in unauthorized access to sensitive data, severely compromising data privacy.
Integrity: High
CVE-2021-37701 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
Availability: None
CVE-2021-37701 does not impact system availability.

Exploit Prediction Scoring System (EPSS)

The EPSS score estimates the probability that this vulnerability will be exploited in the near future.

EPSS Score: 0.157% (probability of exploit)

EPSS Percentile: 53.43% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 46.57% of others.

CVE-2021-37701 References

External References

CWE Common Weakness Enumeration

CWE-59

CAPEC Common Attack Pattern Enumeration and Classification

Symlink Attack CAPEC-132 An adversary positions a symbolic link in such a manner that the targeted user or application accesses the link's endpoint, assuming that it is accessing a file with the link's name.
Using Malicious Files CAPEC-17 An attack of this type exploits a system's configuration that allows an adversary to either directly access an executable file, for example through shell access; or in a possible worst case allows an adversary to upload a file and then execute it. Web servers, ftp servers, and message oriented middleware systems which have many integration points are particularly vulnerable, because both the programmers and the administrators must be in synch regarding the interfaces and the correct privileges for each interface.
Leverage Executable Code in Non-Executable Files CAPEC-35 An attack of this type exploits a system's trust in configuration and resource files. When the executable loads the resource (such as an image file or configuration file) the attacker has modified the file to either execute malicious code directly or manipulate the target process (e.g. application server) to execute based on the malicious configuration parameters. Since systems are increasingly interrelated mashing up resources from local and remote sources the possibility of this attack occurring is high.
Manipulating Web Input to File System Calls CAPEC-76 An attacker manipulates inputs to the target software which the target software passes to file system calls in the OS. The goal is to gain access to, and perhaps modify, areas of the file system that the target software did not intend to be accessible.

Vulnerable Configurations

cpe:2.3:a:npmjs:tar:0.1.0:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:0.1.0:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:0.1.2:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:0.1.2:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:0.1.3:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:0.1.3:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:0.1.5:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:0.1.5:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:0.1.6:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:0.1.6:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:0.1.7:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:0.1.7:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:0.1.8:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:0.1.8:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:0.1.9:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:0.1.9:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:0.1.10:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:0.1.10:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:0.1.11:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:0.1.11:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:0.1.12:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:0.1.12:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:0.1.13:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:0.1.13:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:0.1.14:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:0.1.14:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:0.1.15:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:0.1.15:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:0.1.16:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:0.1.16:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:0.1.17:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:0.1.17:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:0.1.18:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:0.1.18:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:0.1.19:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:0.1.19:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:0.1.20:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:0.1.20:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:1.0.0:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:1.0.0:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:1.0.1:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:1.0.1:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:1.0.2:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:1.0.2:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:1.0.3:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:1.0.3:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:2.0.0:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:2.0.0:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:2.0.1:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:2.0.1:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:2.1.0:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:2.1.0:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:2.1.1:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:2.1.1:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:2.2.1:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:2.2.1:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:2.2.2:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:2.2.2:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:3.0.0:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:3.0.0:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:3.0.1:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:3.0.1:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:3.1.0:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:3.1.0:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:3.1.1:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:3.1.1:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:3.1.2:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:3.1.2:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:3.1.3:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:3.1.3:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:3.1.4:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:3.1.4:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:3.1.5:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:3.1.5:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:3.1.6:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:3.1.6:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:3.1.7:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:3.1.7:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:3.1.8:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:3.1.8:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:3.1.9:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:3.1.9:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:3.1.10:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:3.1.10:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:3.1.11:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:3.1.11:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:3.1.12:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:3.1.12:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:3.1.13:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:3.1.13:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:3.1.14:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:3.1.14:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:3.1.15:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:3.1.15:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:3.2.0:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:3.2.0:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:3.2.1:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:3.2.1:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:3.2.2:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:3.2.2:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:3.2.3:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:3.2.3:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:4.0.0:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:4.0.0:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:4.0.1:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:4.0.1:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:4.0.2:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:4.0.2:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:4.1.0:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:4.1.0:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:4.1.1:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:4.1.1:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:4.1.2:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:4.1.2:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:4.2.0:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:4.2.0:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:4.3.0:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:4.3.0:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:4.3.1:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:4.3.1:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:4.3.2:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:4.3.2:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:4.3.3:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:4.3.3:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:4.4.0:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:4.4.0:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:4.4.1:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:4.4.1:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:4.4.2:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:4.4.2:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:4.4.3:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:4.4.3:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:4.4.4:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:4.4.4:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:4.4.5:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:4.4.5:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:4.4.6:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:4.4.6:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:4.4.7:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:4.4.7:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:4.4.8:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:4.4.8:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:4.4.9:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:4.4.9:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:4.4.10:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:4.4.10:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:4.4.11:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:4.4.11:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:4.4.12:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:4.4.12:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:4.4.13:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:4.4.13:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:4.4.14:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:4.4.14:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:4.4.15:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:4.4.15:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:5.0.0:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:5.0.0:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:5.0.1:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:5.0.1:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:5.0.2:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:5.0.2:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:5.0.3:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:5.0.3:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:5.0.4:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:5.0.4:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:5.0.5:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:5.0.5:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:5.0.6:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:5.0.6:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:5.0.7:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:5.0.7:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:6.0.0:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:6.0.0:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:6.0.1:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:6.0.1:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:6.0.2:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:6.0.2:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:6.0.3:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:6.0.3:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:6.0.4:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:6.0.4:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:6.0.5:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:6.0.5:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:6.1.0:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:6.1.0:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:6.1.1:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:6.1.1:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:6.1.2:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:6.1.2:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:6.1.3:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:6.1.3:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:6.1.4:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:6.1.4:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:6.1.5:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:6.1.5:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:6.1.6:*:*:*:*:node.js:*:*
cpe:2.3:a:npmjs:tar:6.1.6:*:*:*:*:node.js:*:*
cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:*
cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:*
cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:*
cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:*
cpe:2.3:a:oracle:graalvm:20.3.3:*:*:*:enterprise:*:*:*
cpe:2.3:a:oracle:graalvm:20.3.3:*:*:*:enterprise:*:*:*
cpe:2.3:a:oracle:graalvm:21.2.0:*:*:*:enterprise:*:*:*
cpe:2.3:a:oracle:graalvm:21.2.0:*:*:*:enterprise:*:*:*
cpe:2.3:a:siemens:sinec_infrastructure_network_services:-:*:*:*:*:*:*:*
cpe:2.3:a:siemens:sinec_infrastructure_network_services:-:*:*:*:*:*:*:*
cpe:2.3:a:siemens:sinec_infrastructure_network_services:1.0.1:-:*:*:*:*:*:*
cpe:2.3:a:siemens:sinec_infrastructure_network_services:1.0.1:-:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2021-37701: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

CVE-2025-2129 – A vulnerability was found in Mage AI 0.9.75. It has been classified as problematic. This affects an unknown part. The manipulation leads to insecur...
CVE-2025-2127 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla. It has been classified as problematic. Affected is an unknown function of th...
CVE-2025-2126 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla and classified as critical. This issue affects some unknown processing of the...
CVE-2025-2125 – A vulnerability has been found in Control iD RH iD 25.2.25.0 and classified as problematic. This vulnerability affects unknown code of the file /v2...
CVE-2025-2124 – A vulnerability, which was classified as problematic, was found in Control iD RH iD 25.2.25.0. This affects an unknown part of the file /v2/custome...

CVE-2021-37701 Vulnerability Scoring