CVE-2021-37712

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.

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.

Impact

Arbitrary File Creation, Arbitrary File Overwrite, Arbitrary Code Execution

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 two directories 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 directories with two forms of the path that resolve to the same file system entity, followed by a symbolic link with a name in the first form, lastly followed by a file using the second form. It led to bypassing 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.

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 below.

Patches

6.1.9 || 5.0.10 || 4.4.18

Workarounds

Users may work around this vulnerability without upgrading by creating a custom filter method which prevents the extraction of symbolic links.

const tar = require('tar')

tar.x({
  file: 'archive.tgz',
  filter: (file, entry) => {
    if (entry.type === 'SymbolicLink') {
      return false
    } else {
      return true
    }
  }
})

Users are encouraged to upgrade to the latest patched versions, rather than attempt to sanitize tar input themselves.

Fix

The problem is addressed in the following ways, when comparing paths in the directory cache and path reservation systems:

1. The String.normalize('NFKD') method is used to first normalize all unicode to its maximally compatible and multi-code-point form.
2. All slashes are normalized to / on Windows systems (on posix systems, \ is a valid filename character, and thus left intact).
3. When a symbolic link is encountered on Windows systems, the entire directory cache is cleared. Collisions related to use of 8.3 short names to replace directories with other (non-symlink) types of entries may make archives fail to extract properly, but will not result in arbitrary file writes.

Node.js is a software development platform for building fast and scalable network applications in the JavaScript programming language.

The following packages have been upgraded to a later upstream version: nodejs (14.18.2), nodejs-nodemon (2.0.15). (BZ#2027609)

Security Fix(es):

• nodejs-json-schema: Prototype pollution vulnerability (CVE-2021-3918)

• nodejs-ini: Prototype pollution via malicious INI file (CVE-2020-7788)

• nodejs-glob-parent: Regular expression denial of service (CVE-2020-28469)

• nodejs-ansi-regex: Regular expression denial of service (ReDoS) matching ANSI escape codes (CVE-2021-3807)

• normalize-url: ReDoS for data URLs (CVE-2021-33502)

• nodejs-tar: Insufficient symlink protection due to directory cache poisoning using symbolic links allowing arbitrary file creation and overwrite (CVE-2021-37701)

• nodejs-tar: Insufficient symlink protection due to directory cache poisoning using symbolic links allowing arbitrary file creation and overwrite (CVE-2021-37712)

• llhttp: HTTP Request Smuggling due to spaces in headers (CVE-2021-22959)

• llhttp: HTTP Request Smuggling when parsing the body of chunked requests (CVE-2021-22960)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

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.

Node.js is a software development platform for building fast and scalable network applications in the JavaScript programming language.

The following packages have been upgraded to a later upstream version: nodejs (14.18.2), nodejs-nodemon (2.0.15). (BZ#2027609)

Security Fix(es):

• nodejs-json-schema: Prototype pollution vulnerability (CVE-2021-3918)

• nodejs-ini: Prototype pollution via malicious INI file (CVE-2020-7788)

• nodejs-glob-parent: Regular expression denial of service (CVE-2020-28469)

• nodejs-ansi-regex: Regular expression denial of service (ReDoS) matching ANSI escape codes (CVE-2021-3807)

• normalize-url: ReDoS for data URLs (CVE-2021-33502)

• nodejs-tar: Insufficient symlink protection due to directory cache poisoning using symbolic links allowing arbitrary file creation and overwrite (CVE-2021-37701)

• nodejs-tar: Insufficient symlink protection due to directory cache poisoning using symbolic links allowing arbitrary file creation and overwrite (CVE-2021-37712)

• llhttp: HTTP Request Smuggling due to spaces in headers (CVE-2021-22959)

• llhttp: HTTP Request Smuggling when parsing the body of chunked requests (CVE-2021-22960)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

TuxCare rebuilt tar to address 2 CVEs. Fixed in 6.0.2-tuxcare.3.

TuxCare rebuilt tar to address 8 CVEs. Fixed in 6.1.6-tuxcare.1.

TuxCare rebuilt tar to address 9 CVEs. Fixed in 6.1.0-tuxcare.2.

Multiple security fixes for nodejs. See references for details

Untrusted tar file to symlink into an arbitrary location allowing file overwrites. (CVE-2021-37712)

Arbitrary file creation/overwrite and arbitrary code execution. (CVE-2021-37701)

Arbitrary File Creation/Overwrite vulnerability via insufficient symlink protection. (CVE-2021-32803)

Arbitrary File Creation/Overwrite vulnerability due to insufficient absolute path sanitization (CVE-2021-32804)

This update for nodejs14 fixes the following issues:

nodejs14 was updated to 14.18.1:

• deps: update llhttp to 2.1.4

  • HTTP Request Smuggling due to spaced in headers (bsc#1191601, CVE-2021-22959)
  • HTTP Request Smuggling when parsing the body (bsc#1191602, CVE-2021-22960)

Changes in 14.18.0:

• buffer:

  • introduce Blob
  • add base64url encoding option

• child_process:

  • allow options.cwd receive a URL
  • add timeout to spawn and fork
  • allow promisified exec to be cancel
  • add 'overlapped' stdio flag

• dns: add 'tries' option to Resolve options

• fs:

  • allow empty string for temp directory prefix
  • allow no-params fsPromises fileHandle read
  • add support for async iterators to fsPromises.writeFile

• http2: add support for sensitive headers

• process: add 'worker' event

• tls: allow reading data into a static buffer

• worker: add setEnvironmentData/getEnvironmentData

Changes in 14.17.6

• deps: upgrade npm to 6.14.15 which fixes a number of security issues (bsc#1190057, CVE-2021-37701, bsc#1190056, CVE-2021-37712, bsc#1190055, CVE-2021-37713, bsc#1190054, CVE-2021-39134, bsc#1190053, CVE-2021-39135)

This update was imported from the SUSE:SLE-15-SP2:Update update project.

This update for nodejs12 fixes the following issues:

• CVE-2021-22959: Fixed HTTP Request Smuggling due to spaced in headers (bsc#1191601).
• CVE-2021-22960: Fixed HTTP Request Smuggling when parsing the body (bsc#1191602).
• CVE-2021-37701: Fixed arbitrary file creation and overwrite in nodejs-tar (bsc#1190057).
• CVE-2021-37712: Fixed arbitrary file creation and overwrite in nodejs-tar (bsc#1190056).
• CVE-2021-37713: Fixed arbitrary code execution and file creation and overwrite in nodejs-tar (bsc#1190055).
• CVE-2021-39134: Fixed symling following vulnerability in nodejs-arborist (bsc#1190054).
• CVE-2021-39135: Fixed symling following vulnerability in nodejs-arborist (bsc#1190053).

This update was imported from the SUSE:SLE-15-SP2:Update update project.

This update for nodejs12 fixes the following issues:

• CVE-2021-22959: Fixed HTTP Request Smuggling due to spaced in headers (bsc#1191601).
• CVE-2021-22960: Fixed HTTP Request Smuggling when parsing the body (bsc#1191602).
• CVE-2021-37701: Fixed arbitrary file creation and overwrite in nodejs-tar (bsc#1190057).
• CVE-2021-37712: Fixed arbitrary file creation and overwrite in nodejs-tar (bsc#1190056).
• CVE-2021-37713: Fixed arbitrary code execution and file creation and overwrite in nodejs-tar (bsc#1190055).
• CVE-2021-39134: Fixed symling following vulnerability in nodejs-arborist (bsc#1190054).
• CVE-2021-39135: Fixed symling following vulnerability in nodejs-arborist (bsc#1190053).

This update for nodejs14 fixes the following issues:

nodejs14 was updated to 14.18.1:

• deps: update llhttp to 2.1.4

  • HTTP Request Smuggling due to spaced in headers (bsc#1191601, CVE-2021-22959)
  • HTTP Request Smuggling when parsing the body (bsc#1191602, CVE-2021-22960)

Changes in 14.18.0:

• buffer:

  • introduce Blob
  • add base64url encoding option

• child_process:

  • allow options.cwd receive a URL
  • add timeout to spawn and fork
  • allow promisified exec to be cancel
  • add 'overlapped' stdio flag

• dns: add 'tries' option to Resolve options

• fs:

  • allow empty string for temp directory prefix
  • allow no-params fsPromises fileHandle read
  • add support for async iterators to fsPromises.writeFile

• http2: add support for sensitive headers

• process: add 'worker' event

• tls: allow reading data into a static buffer

• worker: add setEnvironmentData/getEnvironmentData

Changes in 14.17.6

• deps: upgrade npm to 6.14.15 which fixes a number of security issues (bsc#1190057, CVE-2021-37701, bsc#1190056, CVE-2021-37712, bsc#1190055, CVE-2021-37713, bsc#1190054, CVE-2021-39134, bsc#1190053, CVE-2021-39135)

Root has patched CVE-2021-37712 in the tar package for Root:npm. Multiple fixed versions available.

This update for nodejs14 fixes the following issues:

nodejs14 was updated to 14.18.1:

• deps: update llhttp to 2.1.4

Security fixes:

• HTTP Request Smuggling due to spaced in headers (bsc#1191601, CVE-2021-22959)
• HTTP Request Smuggling when parsing the body (bsc#1191602, CVE-2021-22960)

Changes in 14.18.0:

• buffer:

  • introduce Blob
  • add base64url encoding option

• child_process:

  • allow options.cwd receive a URL
  • add timeout to spawn and fork
  • allow promisified exec to be cancel
  • add 'overlapped' stdio flag

• dns: add 'tries' option to Resolve options

• fs:

  • allow empty string for temp directory prefix
  • allow no-params fsPromises fileHandle read
  • add support for async iterators to fsPromises.writeFile

• http2: add support for sensitive headers

• process: add 'worker' event

• tls: allow reading data into a static buffer

• worker: add setEnvironmentData/getEnvironmentData

Changes in 14.17.6:

• deps: upgrade npm to 6.14.15 which fixes a number of security issues (bsc#1190057, CVE-2021-37701, bsc#1190056, CVE-2021-37712, bsc#1190055, CVE-2021-37713, bsc#1190054, CVE-2021-39134, bsc#1190053, CVE-2021-39135)

This update for nodejs12 fixes the following issues:

• CVE-2021-22959: Fixed HTTP Request Smuggling due to spaced in headers (bsc#1191601).
• CVE-2021-22960: Fixed HTTP Request Smuggling when parsing the body (bsc#1191602).
• CVE-2021-37701: Fixed arbitrary file creation and overwrite in nodejs-tar (bsc#1190057).
• CVE-2021-37712: Fixed arbitrary file creation and overwrite in nodejs-tar (bsc#1190056).
• CVE-2021-37713: Fixed arbitrary code execution and file creation and overwrite in nodejs-tar (bsc#1190055).
• CVE-2021-39134: Fixed symling following vulnerability in nodejs-arborist (bsc#1190054).
• CVE-2021-39135: Fixed symling following vulnerability in nodejs-arborist (bsc#1190053).

This update for nodejs14 fixes the following issues:

nodejs14 was updated to 14.18.1:

• deps: update llhttp to 2.1.4

  • HTTP Request Smuggling due to spaced in headers (bsc#1191601, CVE-2021-22959)
  • HTTP Request Smuggling when parsing the body (bsc#1191602, CVE-2021-22960)

Changes in 14.18.0:

• buffer:

  • introduce Blob
  • add base64url encoding option

• child_process:

  • allow options.cwd receive a URL
  • add timeout to spawn and fork
  • allow promisified exec to be cancel
  • add 'overlapped' stdio flag

• dns: add 'tries' option to Resolve options

• fs:

  • allow empty string for temp directory prefix
  • allow no-params fsPromises fileHandle read
  • add support for async iterators to fsPromises.writeFile

• http2: add support for sensitive headers

• process: add 'worker' event

• tls: allow reading data into a static buffer

• worker: add setEnvironmentData/getEnvironmentData

Changes in 14.17.6

• deps: upgrade npm to 6.14.15 which fixes a number of security issues (bsc#1190057, CVE-2021-37701, bsc#1190056, CVE-2021-37712, bsc#1190055, CVE-2021-37713, bsc#1190054, CVE-2021-39134, bsc#1190053, CVE-2021-39135)

This update for nodejs12 fixes the following issues:

• CVE-2021-44531: Fixed improper handling of URI Subject Alternative Names (bsc#1194511).
• CVE-2021-44532: Fixed certificate Verification Bypass via String Injection (bsc#1194512).
• CVE-2021-44533: Fixed incorrect handling of certificate subject and issuer fields (bsc#1194513).
• CVE-2022-21824: Fixed prototype pollution via console.table properties (bsc#1194514).
• CVE-2021-22959: Fixed HTTP Request Smuggling due to spaced in headers(bsc#1191601).
• CVE-2021-22960: Fixed HTTP Request Smuggling when parsing the body (bsc#1191602).
• CVE-2021-37701: Fixed arbitrary file creation and overwrite vulnerability in nodejs-tar (bsc#1190057).
• CVE-2021-37712: Fixed arbitrary file creation and overwrite vulnerability in nodejs-tar (bsc#1190056).
• CVE-2021-37713: Fixed arbitrary file creation/overwrite and arbitrary code execution vulnerability in nodejs-tar (bsc#1190055).
• CVE-2021-39134: Fixed symlink following vulnerability in nodejs-arborist (bsc#1190054).
• CVE-2021-39135: Fixed symlink following vulnerability in nodejs-arborist (bsc#1190053).