Improper Certificate Validation Affecting nodejs:16/nodejs-devel package, versions <1:16.18.1-3.module+el8.7.0+17465+1a1abd74


Severity

Recommended
medium

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.52% (78th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL8-NODEJS-4344579
  • published15 Jan 2022
  • disclosed10 Jan 2022

Introduced: 10 Jan 2022

CVE-2021-44533  (opens in a new tab)
CWE-295  (opens in a new tab)
First added by Snyk

How to fix?

Upgrade RHEL:8 nodejs:16/nodejs-devel to version 1:16.18.1-3.module+el8.7.0+17465+1a1abd74 or higher.
This issue was patched in RHSA-2022:9073.

NVD Description

Note: Versions mentioned in the description apply only to the upstream nodejs:16/nodejs-devel package and not the nodejs:16/nodejs-devel package as distributed by RHEL. See How to fix? for RHEL:8 relevant fixed versions and status.

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.

CVSS Scores

version 3.1