CVE-2021-44533

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.

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.

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…

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

Security Fix(es):

• nodejs: Improper handling of URI Subject Alternative Names (CVE-2021-44531)

• nodejs: Certificate Verification Bypass via String Injection (CVE-2021-44532)

• nodejs: Incorrect handling of certificate subject and issuer fields (CVE-2021-44533)

• nodejs: HTTP Request Smuggling due to incorrect parsing of header fields (CVE-2022-35256)

• nodejs: Prototype pollution via console.table properties (CVE-2022-21824)

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.

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

The following packages were updated to later upstream versions: nodejs (16.18.1), nodejs-nodemon (2.0.20).

Security Fix(es):

• nodejs: Improper handling of URI Subject Alternative Names (CVE-2021-44531)

• nodejs: Certificate Verification Bypass via String Injection (CVE-2021-44532)

• nodejs: Incorrect handling of certificate subject and issuer fields (CVE-2021-44533)

• minimist: prototype pollution (CVE-2021-44906)

• nodejs-minimatch: ReDoS via the braceExpand function (CVE-2022-3517)

• nodejs: DNS rebinding in inspect via invalid octal IP address (CVE-2022-43548)

• nodejs: Prototype pollution via console.table properties (CVE-2022-21824)

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.

Bug Fix(es):

• nodejs:16/nodejs: Packaged version of undici does not fit with declared version. [Rocky Linux-8] (BZ#2151625)

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.

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

Security Fix(es):

• nodejs: Improper handling of URI Subject Alternative Names (CVE-2021-44531)
• nodejs: Certificate Verification Bypass via String Injection (CVE-2021-44532)
• nodejs: Incorrect handling of certificate subject and issuer fields (CVE-2021-44533)
• nodejs: HTTP Request Smuggling due to incorrect parsing of header fields (CVE-2022-35256)
• nodejs: Prototype pollution via console.table properties (CVE-2022-21824)

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.

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

The following packages were updated to later upstream versions: nodejs (16.18.1), nodejs-nodemon (2.0.20).

Security Fix(es):

• nodejs: Improper handling of URI Subject Alternative Names (CVE-2021-44531)
• nodejs: Certificate Verification Bypass via String Injection (CVE-2021-44532)
• nodejs: Incorrect handling of certificate subject and issuer fields (CVE-2021-44533)
• minimist: prototype pollution (CVE-2021-44906)
• nodejs-minimatch: ReDoS via the braceExpand function (CVE-2022-3517)
• nodejs: DNS rebinding in inspect via invalid octal IP address (CVE-2022-43548)
• nodejs: Prototype pollution via console.table properties (CVE-2022-21824)

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.

Bug Fix(es):

• nodejs:16/nodejs: Packaged version of undici does not fit with declared version. [almalinux-8] (BZ#2151625)

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.

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.

Improper handling of URI Subject Alternative Names (Medium). 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 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 with the fix for this disable the URI SAN type when checking a certificate against a hostname. This behavior can be reverted through the --security-revert command-line option. (CVE-2021-44531)

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

Due to the formatting logic of the console.table() function it was not safe to allow user controlled input to be passed to the properties parameter while simultaneously passing a plain object with at least one property as the first parameter, which could be proto. The prototype pollution has very limited control, in that it only allows an empty string to be assigned to numerical keys of the object prototype. Versions of Node.js with the fix for this use a null protoype for the object these properties are being assigned to. (CVE-2022-21824)

This update for nodejs14 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).

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

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

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

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

This update for nodejs14 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).

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

This update for nodejs14 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).