search

turkdevops / node

Node.js JavaScript runtime :sparkles::turtle::rocket::sparkles:
https://nodejs.org/
Other
0 stars 0 forks source link

CVE-2021-32804 (High) detected in tar-5.0.5.tgz, tar-4.4.13.tgz #325

Open mend-bolt-for-github[bot] opened 3 years ago

mend-bolt-for-github[bot] commented 3 years ago

CVE-2021-32804 - High Severity Vulnerability

Vulnerable Libraries - tar-5.0.5.tgz, tar-4.4.13.tgz

tar-5.0.5.tgz

tar for node

Library home page: https://registry.npmjs.org/tar/-/tar-5.0.5.tgz

Path to dependency file: /deps/npm/docs/package.json

Path to vulnerable library: /deps/npm/docs/package.json

Dependency Hierarchy: - gatsby-plugin-manifest-2.2.34.tgz (Root Library) - sharp-0.23.4.tgz - :x: **tar-5.0.5.tgz** (Vulnerable Library)

tar-4.4.13.tgz

tar for node

Library home page: https://registry.npmjs.org/tar/-/tar-4.4.13.tgz

Path to dependency file: /deps/npm/package.json

Path to vulnerable library: /deps/npm/node_modules/tar/package.json

Dependency Hierarchy: - :x: **tar-4.4.13.tgz** (Vulnerable Library)

Found in HEAD commit: 034a6d9c041d2f56d0c835c69088ea8b954f0b5f

Found in base branch: master

Vulnerability Details

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

CVSS 3 Score Details (8.1)

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.

Suggested Fix

Type: Upgrade version

Origin: https://github.com/npm/node-tar/security/advisories/GHSA-3jfq-g458-7qm9

Release Date: 2021-08-03

Fix Resolution (tar): 5.0.6

Direct dependency fix Resolution (gatsby-plugin-manifest): 2.2.36

Step up your Open Source Security Game with Mend here

mend-bolt-for-github[bot] commented 1 year ago

:heavy_check_mark: This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory.

mend-bolt-for-github[bot] commented 1 year ago

:information_source: This issue was automatically re-opened by Mend because the vulnerable library in the specific branch(es) has been detected in the Mend inventory.