CVE-2021-39135

@npmcli/arborist, the library that calculates dependency trees and manages the node_modules folder hierarchy for the npm command line interface, aims to guarantee that package dependency contracts will be met, and the extraction of package contents will always be performed into the expected folder. This is accomplished by extracting package contents into a project's node_modules folder. If the node_modules folder of the root project or any of its dependencies is somehow replaced with a symbolic link, it could allow Arborist to write package dependencies to any arbitrary location on the file system. Note that symbolic links contained within package artifact contents are filtered out, so another means of creating a node_modules symbolic link would have to be employed. 1. A preinstall script could replace node_modules with a symlink. (This is prevented by using --ignore-scripts.) 2. An attacker could supply the target with a git repository, instructing them to run npm install --ignore-scripts in the root. This may be successful, because npm install --ignore-scripts is typically not capable of making changes outside of the project directory, so it may be deemed safe. This is patched in @npmcli/arborist 2.8.2 which is included in npm v7.20.7 and above. For more information including workarounds please see the referenced GHSA-gmw6-94gg-2rc2.

@npmcli/arborist, the library that calculates dependency trees and manages the node_modules folder hierarchy for the npm command line interface, aims to guarantee that package dependency contracts will be met, and the extraction of package contents will always be performed into the expected folder. This is accomplished by extracting package contents into a project's node_modules folder. If the node_modules folder of the root project or any of its dependencies is somehow replaced with a symbolic link, it could allow Arborist to write package dependencies to any arbitrary location on the file system. Note that symbolic links contained within package artifact contents are filtered out, so another means of creating a node_modules symbolic link would have to be employed. 1. A preinstall script could replace node_modules with a symlink. (This is prevented by using --ignore-scripts.) 2. An attacker could supply the target with a git repository, instructing them to run npm install --ignore-scripts in the root. This may be successful, because npm install --ignore-scripts is typically not capable of making changes outside of the project directory, so it may be deemed safe. This is patched in @npmcli/arborist 2.8.2 which is included in npm v7.20.7 and above. For more information including workarounds please see the referenced GHSA-gmw6-94gg-2rc2.

Impact

Arbitrary File Creation, Arbitrary File Overwrite, Arbitrary Code Execution

@npmcli/arborist, the library that calculates dependency trees and manages the node_modules folder hierarchy for the npm command line interface, aims to guarantee that package dependency contracts will be met, and the extraction of package contents will always be performed into the expected folder.

This is accomplished by extracting package contents into a project's node_modules folder.

If the node_modules folder of the root project or any of its dependencies is somehow replaced with a symbolic link, it could allow Arborist to write package dependencies to any arbitrary location on the file system.

Note that symbolic links contained within package artifact contents are filtered out, so another means of creating a node_modules symbolic link would have to be employed.

1. A preinstall script could replace node_modules with a symlink. (This is prevented by using --ignore-scripts.)
2. An attacker could supply the target with a git repository, instructing them to run npm install --ignore-scripts in the root. This may be successful, because npm install --ignore-scripts is typically not capable of making changes outside of the project directory, so it may be deemed safe.

Patches

2.8.2 (included in npm v7.20.7 and above)

Workarounds

Do not run npm install on untrusted codebases, without first ensuring that the node_modules directory in the project is not a symbolic link.

Fix

Prior to extracting any package contents, the node_modules folder into which it is extracted is verified to be a real directory. If it is not, then it is removed.

Caveat: if you are currently relying on creating a symbolic link to the node_modules folder in order to share dependencies between projects, then that will no longer be possible. Please use the npm link command, explicit file:... dependencies, and/or workspaces to share dependencies in a development environment.

Node.js is a platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications. Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices.

Security Fix(es):

An issue was discovered in ajv.validate() in Ajv (aka Another JSON Schema Validator) 6.12.2. A carefully crafted JSON schema could be provided that allows execution of other code by prototype pollution. (While untrusted schemas are recommended against, the worst case of an untrusted schema should be a denial of service, not execution of code.)(CVE-2020-15366)

The X509_V_FLAG_X509_STRICT flag enables additional security checks of the certificates present in a certificate chain. It is not set by default. Starting from OpenSSL version 1.1.1h a check to disallow certificates in the chain that have explicitly encoded elliptic curve parameters was added as an additional strict check. An error in the implementation of this check meant that the result of a previous check to confirm that certificates in the chain are valid CA certificates was overwritten. This effectively bypasses the check that non-CA certificates must not be able to issue other certificates. If a "purpose" has been configured then there is a subsequent opportunity for checks that the certificate is a valid CA. All of the named "purpose" values implemented in libcrypto perform this check. Therefore, where a purpose is set the certificate chain will still be rejected even when the strict flag has been used. A purpose is set by default in libssl client and server certificate verification routines, but it can be overridden or removed by an application. In order to be affected, an application must explicitly set the X509_V_FLAG_X509_STRICT verification flag and either not set a purpose for the certificate verification or, in the case of TLS client or server applications, override the default purpose. OpenSSL versions 1.1.1h and newer are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1k. OpenSSL 1.0.2 is not impacted by this issue. Fixed in OpenSSL 1.1.1k (Affected 1.1.1h-1.1.1j).(CVE-2021-3450)

Node.js < 12.22.9, < 14.18.3, < 16.13.2, and < 17.3.1 converts SANs (Subject Alternative Names) to a string format. It uses this string to check peer certificates against hostnames when validating connections. The string format was subject to an injection vulnerability when name constraints were used within a certificate chain, allowing the bypass of these name constraints.Versions of Node.js with the fix for this escape SANs containing the problematic characters in order to prevent the injection. This behavior can be reverted through the --security-revert command-line option.(CVE-2021-44532)

Node.js < 12.22.9, < 14.18.3, < 16.13.2, and < 17.3.1 did not handle multi-value Relative Distinguished Names correctly. Attackers could craft certificate subjects containing a single-value Relative Distinguished Name that would be interpreted as a multi-value Relative Distinguished Name, for example, in order to inject a Common Name that would allow bypassing the certificate subject verification.Affected versions of Node.js that do not accept multi-value Relative Distinguished Names and are thus not vulnerable to such attacks themselves. However, third-party code that uses node's ambiguous presentation of certificate subjects may be vulnerable.(CVE-2021-44533)

Accepting arbitrary Subject Alternative Name (SAN) types, unless a PKI is specifically defined to use a particular SAN type, can result in bypassing name-constrained intermediates. Node.js < 12.22.9, < 14.18.3, < 16.13.2, and < 17.3.1 was accepting URI SAN types, which PKIs are often not defined to use. Additionally, when a protocol allows URI SANs, Node.js did not match the URI correctly.Versions of Node.js…

@npmcli/arborist, the library that calculates dependency trees and manages the node_modules folder hierarchy for the npm command line interface, aims to guarantee that package dependency contracts will be met, and the extraction of package contents will always be performed into the expected folder. This is accomplished by extracting package contents into a project's node_modules folder. If the node_modules folder of the root project or any of its dependencies is somehow replaced with a symbolic link, it could allow Arborist to write package dependencies to any arbitrary location on the file system. Note that symbolic links contained within package artifact contents are filtered out, so another means of creating a node_modules symbolic link would have to be employed. 1. A preinstall script could replace node_modules with a symlink. (This is prevented by using --ignore-scripts.) 2. An attacker could supply the target with a git repository, instructing them to run npm install --ignore-scripts in the root. This may be successful, because npm install --ignore-scripts is typically not capable of making changes outside of the project directory, so it may be deemed safe. This is patched in @npmcli/arborist 2.8.2 which is included in npm v7.20.7 and above. For more information including workarounds please see the referenced GHSA-gmw6-94gg-2rc2.

Multiple security fixes for nodejs. See references for details

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)

These are all security issues fixed in the nodejs14-14.18.1-1.1 package on the GA media of openSUSE Tumbleweed.

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