📂 Vulnerable Library - terser-webpack-plugin-4.2.3.tgz
Terser plugin for webpack
Path to dependency file: /src/Administration/Resources/app/administration/package.json
Findings
| Finding |
Severity |
🎯 CVSS |
Exploit Maturity |
EPSS |
Library |
Type |
Fixed in |
Remediation Available |
Reachability |
| CVE-2021-37701 |
🟣 Critical |
9.2 |
Not Defined |
< 1% |
tar-6.1.6.tgz |
Transitive |
N/A |
❌ |
|
| CVE-2021-37712 |
🟣 Critical |
9.2 |
Not Defined |
< 1% |
tar-6.1.6.tgz |
Transitive |
N/A |
❌ |
|
| CVE-2021-37713 |
🟣 Critical |
9.2 |
Not Defined |
< 1% |
tar-6.1.6.tgz |
Transitive |
N/A |
❌ |
|
| CVE-2022-25858 |
🟠 Medium |
6.9 |
Not Defined |
2.8000002% |
terser-5.6.0.tgz |
Transitive |
N/A |
❌ |
|
Details
🟣CVE-2021-37701
Vulnerable Library - tar-6.1.6.tgz
tar for node
Library home page: https://registry.npmjs.org/tar/-/tar-6.1.6.tgz
Path to dependency file: /src/Administration/Resources/app/administration/package.json
Dependency Hierarchy:
Vulnerability Details
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.
Mend Note: The description of this vulnerability differs from MITRE.
Publish Date: Aug 31, 2021 12:00 AM
URL: CVE-2021-37701
Threat Assessment
Exploit Maturity:Not Defined
EPSS:< 1%
Score: 9.2
Suggested Fix
Type: Upgrade version
Origin: GHSA-9r2w-394v-53qc
Release Date: Aug 31, 2021 12:00 AM
Fix Resolution : tar - 5.0.8,tar - 4.4.16,tar - 6.1.7
🟣CVE-2021-37712
Vulnerable Library - tar-6.1.6.tgz
tar for node
Library home page: https://registry.npmjs.org/tar/-/tar-6.1.6.tgz
Path to dependency file: /src/Administration/Resources/app/administration/package.json
Dependency Hierarchy:
Vulnerability Details
The npm package "tar" (aka node-tar) before versions 4.4.18, 5.0.10, and 6.1.9 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 names containing unicode values that normalized to the same value. Additionally, on Windows systems, long path portions would resolve to the same file system entities as their 8.3 "short path" counterparts. A specially crafted tar archive could thus include a directory with one form of the path, followed by a symbolic link with a different string that resolves to the same file system entity, followed by a file using the first form. By first creating a directory, and then replacing that directory with a symlink that had a different apparent name that resolved to the same entry in the filesystem, 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. These issues were addressed in releases 4.4.18, 5.0.10 and 6.1.9. 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-qq89-hq3f-393p.
Publish Date: Aug 31, 2021 12:00 AM
URL: CVE-2021-37712
Threat Assessment
Exploit Maturity:Not Defined
EPSS:< 1%
Score: 9.2
Suggested Fix
Type: Upgrade version
Origin: GHSA-qq89-hq3f-393p
Release Date: Aug 31, 2021 12:00 AM
Fix Resolution : tar - 5.0.10,tar - 4.4.18,tar - 6.1.9
🟣CVE-2021-37713
Vulnerable Library - tar-6.1.6.tgz
tar for node
Library home page: https://registry.npmjs.org/tar/-/tar-6.1.6.tgz
Path to dependency file: /src/Administration/Resources/app/administration/package.json
Dependency Hierarchy:
Vulnerability Details
The npm package "tar" (aka node-tar) before versions 4.4.18, 5.0.10, and 6.1.9 has an arbitrary file creation/overwrite and arbitrary code execution vulnerability. node-tar aims to guarantee that any file whose location would be outside of the extraction target directory is not extracted. This is, in part, accomplished by sanitizing absolute paths of entries within the archive, skipping archive entries that contain ".." path portions, and resolving the sanitized paths against the extraction target directory. This logic was insufficient on Windows systems when extracting tar files that contained a path that was not an absolute path, but specified a drive letter different from the extraction target, such as "C:some\path". If the drive letter does not match the extraction target, for example "D:\extraction\dir", then the result of "path.resolve(extractionDirectory, entryPath)" would resolve against the current working directory on the "C:" drive, rather than the extraction target directory. Additionally, a ".." portion of the path could occur immediately after the drive letter, such as "C:../foo", and was not properly sanitized by the logic that checked for ".." within the normalized and split portions of the path. This only affects users of "node-tar" on Windows systems. These issues were addressed in releases 4.4.18, 5.0.10 and 6.1.9. 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. There is no reasonable way to work around this issue without performing the same path normalization procedures that node-tar now does. Users are encouraged to upgrade to the latest patched versions of node-tar, rather than attempt to sanitize paths themselves.
Mend Note: The description of this vulnerability differs from MITRE.
Publish Date: Aug 31, 2021 04:50 PM
URL: CVE-2021-37713
Threat Assessment
Exploit Maturity:Not Defined
EPSS:< 1%
Score: 9.2
Suggested Fix
Type: Upgrade version
Origin: GHSA-5955-9wpr-37jh
Release Date: Aug 31, 2021 04:50 PM
Fix Resolution : tar - 6.1.9,tar - 5.0.10,tar - 4.4.18
🟠CVE-2022-25858
Vulnerable Library - terser-5.6.0.tgz
JavaScript parser, mangler/compressor and beautifier toolkit for ES6+
Library home page: https://registry.npmjs.org/terser/-/terser-5.6.0.tgz
Path to dependency file: /src/Administration/Resources/app/administration/package.json
Dependency Hierarchy:
- terser-webpack-plugin-4.2.3.tgz (Root Library)
- ❌ terser-5.6.0.tgz (Vulnerable Library)
Vulnerability Details
The package terser before 4.8.1, from 5.0.0 and before 5.14.2 are vulnerable to Regular Expression Denial of Service (ReDoS) due to insecure usage of regular expressions.
Publish Date: Jul 15, 2022 08:00 PM
URL: CVE-2022-25858
Threat Assessment
Exploit Maturity:Not Defined
EPSS:2.8000002%
Score: 6.9
Suggested Fix
Type: Upgrade version
Origin: GHSA-4wf5-vphf-c2xc
Release Date: Jul 15, 2022 08:00 PM
Fix Resolution : terser - 4.8.1,terser - 5.14.2
📂 Vulnerable Library - terser-webpack-plugin-4.2.3.tgz
Terser plugin for webpack
Path to dependency file: /src/Administration/Resources/app/administration/package.json
Findings
Details
🟣CVE-2021-37701
Vulnerable Library - tar-6.1.6.tgz
tar for node
Library home page: https://registry.npmjs.org/tar/-/tar-6.1.6.tgz
Path to dependency file: /src/Administration/Resources/app/administration/package.json
Dependency Hierarchy:
terser-webpack-plugin-4.2.3.tgz (Root Library)
copy-webpack-plugin-6.4.1.tgz (Root Library)
Vulnerability Details
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.
Mend Note: The description of this vulnerability differs from MITRE.
Publish Date: Aug 31, 2021 12:00 AM
URL: CVE-2021-37701
Threat Assessment
Exploit Maturity:Not Defined
EPSS:< 1%
Score: 9.2
Suggested Fix
Type: Upgrade version
Origin: GHSA-9r2w-394v-53qc
Release Date: Aug 31, 2021 12:00 AM
Fix Resolution : tar - 5.0.8,tar - 4.4.16,tar - 6.1.7
🟣CVE-2021-37712
Vulnerable Library - tar-6.1.6.tgz
tar for node
Library home page: https://registry.npmjs.org/tar/-/tar-6.1.6.tgz
Path to dependency file: /src/Administration/Resources/app/administration/package.json
Dependency Hierarchy:
terser-webpack-plugin-4.2.3.tgz (Root Library)
copy-webpack-plugin-6.4.1.tgz (Root Library)
Vulnerability Details
The npm package "tar" (aka node-tar) before versions 4.4.18, 5.0.10, and 6.1.9 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 names containing unicode values that normalized to the same value. Additionally, on Windows systems, long path portions would resolve to the same file system entities as their 8.3 "short path" counterparts. A specially crafted tar archive could thus include a directory with one form of the path, followed by a symbolic link with a different string that resolves to the same file system entity, followed by a file using the first form. By first creating a directory, and then replacing that directory with a symlink that had a different apparent name that resolved to the same entry in the filesystem, 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. These issues were addressed in releases 4.4.18, 5.0.10 and 6.1.9. 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-qq89-hq3f-393p.
Publish Date: Aug 31, 2021 12:00 AM
URL: CVE-2021-37712
Threat Assessment
Exploit Maturity:Not Defined
EPSS:< 1%
Score: 9.2
Suggested Fix
Type: Upgrade version
Origin: GHSA-qq89-hq3f-393p
Release Date: Aug 31, 2021 12:00 AM
Fix Resolution : tar - 5.0.10,tar - 4.4.18,tar - 6.1.9
🟣CVE-2021-37713
Vulnerable Library - tar-6.1.6.tgz
tar for node
Library home page: https://registry.npmjs.org/tar/-/tar-6.1.6.tgz
Path to dependency file: /src/Administration/Resources/app/administration/package.json
Dependency Hierarchy:
terser-webpack-plugin-4.2.3.tgz (Root Library)
copy-webpack-plugin-6.4.1.tgz (Root Library)
Vulnerability Details
The npm package "tar" (aka node-tar) before versions 4.4.18, 5.0.10, and 6.1.9 has an arbitrary file creation/overwrite and arbitrary code execution vulnerability. node-tar aims to guarantee that any file whose location would be outside of the extraction target directory is not extracted. This is, in part, accomplished by sanitizing absolute paths of entries within the archive, skipping archive entries that contain ".." path portions, and resolving the sanitized paths against the extraction target directory. This logic was insufficient on Windows systems when extracting tar files that contained a path that was not an absolute path, but specified a drive letter different from the extraction target, such as "C:some\path". If the drive letter does not match the extraction target, for example "D:\extraction\dir", then the result of "path.resolve(extractionDirectory, entryPath)" would resolve against the current working directory on the "C:" drive, rather than the extraction target directory. Additionally, a ".." portion of the path could occur immediately after the drive letter, such as "C:../foo", and was not properly sanitized by the logic that checked for ".." within the normalized and split portions of the path. This only affects users of "node-tar" on Windows systems. These issues were addressed in releases 4.4.18, 5.0.10 and 6.1.9. 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. There is no reasonable way to work around this issue without performing the same path normalization procedures that node-tar now does. Users are encouraged to upgrade to the latest patched versions of node-tar, rather than attempt to sanitize paths themselves.
Mend Note: The description of this vulnerability differs from MITRE.
Publish Date: Aug 31, 2021 04:50 PM
URL: CVE-2021-37713
Threat Assessment
Exploit Maturity:Not Defined
EPSS:< 1%
Score: 9.2
Suggested Fix
Type: Upgrade version
Origin: GHSA-5955-9wpr-37jh
Release Date: Aug 31, 2021 04:50 PM
Fix Resolution : tar - 6.1.9,tar - 5.0.10,tar - 4.4.18
🟠CVE-2022-25858
Vulnerable Library - terser-5.6.0.tgz
JavaScript parser, mangler/compressor and beautifier toolkit for ES6+
Library home page: https://registry.npmjs.org/terser/-/terser-5.6.0.tgz
Path to dependency file: /src/Administration/Resources/app/administration/package.json
Dependency Hierarchy:
Vulnerability Details
The package terser before 4.8.1, from 5.0.0 and before 5.14.2 are vulnerable to Regular Expression Denial of Service (ReDoS) due to insecure usage of regular expressions.
Publish Date: Jul 15, 2022 08:00 PM
URL: CVE-2022-25858
Threat Assessment
Exploit Maturity:Not Defined
EPSS:2.8000002%
Score: 6.9
Suggested Fix
Type: Upgrade version
Origin: GHSA-4wf5-vphf-c2xc
Release Date: Jul 15, 2022 08:00 PM
Fix Resolution : terser - 4.8.1,terser - 5.14.2