The npm package "tar" (aka node-tar) before versions 6.1.1, 5.0.6, 4.4.14, and 3.3.2 has a arbitrary File Creation/Overwrite vulnerability due to insufficient absolute path sanitization. node-tar aims to prevent extraction of absolute file paths by turning absolute paths into relative paths when the `preservePaths` flag is not set to `true`. This is achieved by stripping the absolute path root from any absolute file paths contained in a tar file. For example `/home/user/.bashrc` would turn into `home/user/.bashrc`. This logic was insufficient when file paths contained repeated path roots such as `////home/user/.bashrc`. `node-tar` would only strip a single path root from such paths. When given an absolute file path with repeating path roots, the resulting path (e.g. `///home/user/.bashrc`) would still resolve to an absolute path, thus allowing arbitrary file creation and overwrite. This issue was addressed in releases 3.2.2, 4.4.14, 5.0.6 and 6.1.1. Users may work around this vulnerability without upgrading by creating a custom `onentry` method which sanitizes the `entry.path` or a `filter` method which removes entries with absolute paths. See referenced GitHub Advisory for details. Be aware of CVE-2021-32803 which fixes a similar bug in later versions of tar.
CVE-2021-32804 - High Severity Vulnerability
tar-4.4.2.tgz
tar for node
Library home page: https://registry.npmjs.org/tar/-/tar-4.4.2.tgz
Path to dependency file: /Ceres/package.json
Path to vulnerable library: /node_modules/@firebase/firestore/node_modules/grpc/node_modules/tar/package.json
Dependency Hierarchy: - firestore-0.5.3.tgz (Root Library) - grpc-1.11.3.tgz - node-pre-gyp-0.10.0.tgz - :x: **tar-4.4.2.tgz** (Vulnerable Library)
tar-2.2.1.tgz
tar for node
Library home page: https://registry.npmjs.org/tar/-/tar-2.2.1.tgz
Path to dependency file: /Ceres/package.json
Path to vulnerable library: /functions/node_modules/grpc/node_modules/tar/package.json
Dependency Hierarchy: - build-angular-0.6.3.tgz (Root Library) - node-sass-4.9.0.tgz - node-gyp-3.6.2.tgz - :x: **tar-2.2.1.tgz** (Vulnerable Library)
Found in HEAD commit: b31d728670f7b1cea140b9a346bf71d1a9771fb2
Found in base branch: clean_branch
The npm package "tar" (aka node-tar) before versions 6.1.1, 5.0.6, 4.4.14, and 3.3.2 has a arbitrary File Creation/Overwrite vulnerability due to insufficient absolute path sanitization. node-tar aims to prevent extraction of absolute file paths by turning absolute paths into relative paths when the `preservePaths` flag is not set to `true`. This is achieved by stripping the absolute path root from any absolute file paths contained in a tar file. For example `/home/user/.bashrc` would turn into `home/user/.bashrc`. This logic was insufficient when file paths contained repeated path roots such as `////home/user/.bashrc`. `node-tar` would only strip a single path root from such paths. When given an absolute file path with repeating path roots, the resulting path (e.g. `///home/user/.bashrc`) would still resolve to an absolute path, thus allowing arbitrary file creation and overwrite. This issue was addressed in releases 3.2.2, 4.4.14, 5.0.6 and 6.1.1. Users may work around this vulnerability without upgrading by creating a custom `onentry` method which sanitizes the `entry.path` or a `filter` method which removes entries with absolute paths. See referenced GitHub Advisory for details. Be aware of CVE-2021-32803 which fixes a similar bug in later versions of tar.
Publish Date: 2021-08-03
URL: CVE-2021-32804
Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: High - Availability Impact: High
For more information on CVSS3 Scores, click here.Type: Upgrade version
Origin: https://github.com/npm/node-tar/security/advisories/GHSA-3jfq-g458-7qm9
Release Date: 2021-08-03
Fix Resolution (tar): 4.4.14
Direct dependency fix Resolution (@firebase/firestore): 0.5.4-0
Fix Resolution (tar): 4.4.14
Direct dependency fix Resolution (@angular-devkit/build-angular): 0.6.4
Step up your Open Source Security Game with Mend here