Improper Certificate Validation Affecting nodejs-full-i18n package, versions <1:12.22.12-1.module+el8.6.0+15324+1f2c5d8d


Severity

Recommended
medium

Based on CentOS 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-CENTOS8-NODEJSFULLI18N-2341626
  • 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 Centos:8 nodejs-full-i18n to version 1:12.22.12-1.module+el8.6.0+15324+1f2c5d8d or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream nodejs-full-i18n package and not the nodejs-full-i18n package as distributed by Centos. See How to fix? for Centos: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