Information Exposure Affecting nodejs:18/npm package, versions <1:9.8.1-1.18.18.2.2.module+el9.2.0.z+20408+7cb5fda5


Severity

Recommended
high

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
2.72% (91st 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-RHEL9-NODEJS-5971464
  • published17 Oct 2023
  • disclosed12 Oct 2023

Introduced: 12 Oct 2023

CVE-2023-45143  (opens in a new tab)
CWE-200  (opens in a new tab)

How to fix?

Upgrade RHEL:9 nodejs:18/npm to version 1:9.8.1-1.18.18.2.2.module+el9.2.0.z+20408+7cb5fda5 or higher.
This issue was patched in RHSA-2023:5849.

NVD Description

Note: Versions mentioned in the description apply only to the upstream nodejs:18/npm package and not the nodejs:18/npm package as distributed by RHEL. See How to fix? for RHEL:9 relevant fixed versions and status.

Undici is an HTTP/1.1 client written from scratch for Node.js. Prior to version 5.26.2, Undici already cleared Authorization headers on cross-origin redirects, but did not clear Cookie headers. By design, cookie headers are forbidden request headers, disallowing them to be set in RequestInit.headers in browser environments. Since undici handles headers more liberally than the spec, there was a disconnect from the assumptions the spec made, and undici's implementation of fetch. As such this may lead to accidental leakage of cookie to a third-party site or a malicious attacker who can control the redirection target (ie. an open redirector) to leak the cookie to the third party site. This was patched in version 5.26.2. There are no known workarounds.

CVSS Scores

version 3.1