Improper Certificate Validation Affecting nodejs-full-i18n package, versions <1:14.20.1-2.module+el8.7.0+1071+4bdda2a8


Severity

Recommended
0.0
medium
0
10

Based on Rocky Linux security rating.

Threat Intelligence

EPSS
0.41% (74th 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-ROCKY8-NODEJSFULLI18N-3268504
  • published3 Feb 2023
  • disclosed24 Feb 2022

Introduced: 24 Feb 2022

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

How to fix?

Upgrade Rocky-Linux:8 nodejs-full-i18n to version 1:14.20.1-2.module+el8.7.0+1071+4bdda2a8 or higher.
This issue was patched in RLSA-2022:7830.

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 Rocky-Linux. See How to fix? for Rocky-Linux:8 relevant fixed versions and status.

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.

CVSS Scores

version 3.1