Improper Certificate Validation Affecting nodejs-full-i18n package, versions <1:16.18.1-3.module+el8.7.0+20893+df13f383


Severity

Recommended
0.0
medium
0
10

Based on Oracle Linux security rating.

Threat Intelligence

EPSS
0.28% (69th 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-ORACLE8-NODEJSFULLI18N-3119835
  • published16 Nov 2022
  • disclosed24 Feb 2022

Introduced: 24 Feb 2022

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

How to fix?

Upgrade Oracle:8 nodejs-full-i18n to version 1:16.18.1-3.module+el8.7.0+20893+df13f383 or higher.
This issue was patched in ELSA-2022-9073-1.

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 Oracle. See How to fix? for Oracle: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