Out-of-bounds Read Affecting nodejs-full-i18n package, versions <1:12.22.3-2.module+el8.4.0+20281+eb64e322


Severity

Recommended
0.0
medium
0
10

Based on Oracle Linux security rating.

Threat Intelligence

EPSS
0.14% (51st 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-2587200
  • published10 Apr 2022
  • disclosed12 Jul 2021

Introduced: 12 Jul 2021

CVE-2021-22918  (opens in a new tab)
CWE-125  (opens in a new tab)

How to fix?

Upgrade Oracle:8 nodejs-full-i18n to version 1:12.22.3-2.module+el8.4.0+20281+eb64e322 or higher.
This issue was patched in ELSA-2021-3073.

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 before 16.4.1, 14.17.2, 12.22.2 is vulnerable to an out-of-bounds read when uv__idna_toascii() is used to convert strings to ASCII. The pointer p is read and increased without checking whether it is beyond pe, with the latter holding a pointer to the end of the buffer. This can lead to information disclosures or crashes. This function can be triggered via uv_getaddrinfo().

CVSS Scores

version 3.1