CVE-2023-30589 Affecting nodejs-full-i18n package, versions <1:16.20.1-1.module+el8.8.0+21143+178952bb


Severity

Recommended
medium

Based on Oracle Linux security rating.

Threat Intelligence

EPSS
0.26% (65th 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-5838122
  • published3 Aug 2023
  • disclosed1 Jul 2023

Introduced: 1 Jul 2023

CVE-2023-30589  (opens in a new tab)

How to fix?

Upgrade Oracle:8 nodejs-full-i18n to version 1:16.20.1-1.module+el8.8.0+21143+178952bb or higher.
This issue was patched in ELSA-2023-4537.

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.

The llhttp parser in the http module in Node v20.2.0 does not strictly use the CRLF sequence to delimit HTTP requests. This can lead to HTTP Request Smuggling (HRS).

The CR character (without LF) is sufficient to delimit HTTP header fields in the llhttp parser. According to RFC7230 section 3, only the CRLF sequence should delimit each header-field. This impacts all Node.js active versions: v16, v18, and, v20

References

CVSS Scores

version 3.1