CVE-2023-30589 Affecting nodejs:18/nodejs-full-i18n package, versions <1:18.16.1-1.module+el8.8.0+19438+94e84959


Severity

Recommended
medium

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.21% (60th 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-RHEL8-NODEJS-5832086
  • published6 Jul 2023
  • disclosed20 Jun 2023

Introduced: 20 Jun 2023

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

How to fix?

Upgrade RHEL:8 nodejs:18/nodejs-full-i18n to version 1:18.16.1-1.module+el8.8.0+19438+94e84959 or higher.
This issue was patched in RHSA-2023:4536.

NVD Description

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

CVSS Scores

version 3.1