Improper Certificate Validation Affecting nodejs:12/npm package, versions <1:6.14.16-1.12.22.12.1.module+el8.2.0+15322+a70ca0ab


Severity

Recommended
0.0
high
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.26% (66th 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-3417622
  • published15 Jan 2022
  • disclosed10 Jan 2022

Introduced: 10 Jan 2022

CVE-2021-44531  (opens in a new tab)
CWE-295  (opens in a new tab)

How to fix?

Upgrade RHEL:8 nodejs:12/npm to version 1:6.14.16-1.12.22.12.1.module+el8.2.0+15322+a70ca0ab or higher.
This issue was patched in RHEA-2022:5221.

NVD Description

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

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

CVSS Scores

version 3.1