CVE-2023-38552: Integrity checks according to policies can be circumvented

Published Oct 13, 2023
·
Updated

Integrity checks according to experimental policies can be circumvented (Medium)

Other sources

Node.js could allow a remote attacker to bypass security restrictions, caused by the circumvention of integrity checks by the policy feature. By sending a specially crafted request, an attacker could exploit this vulnerability to bypass the experimental permission model.

— IBM

When the Node.js policy feature checks the integrity of a resource against a trusted manifest, the application can intercept the operation and return a forged checksum to node's policy implementation, thus effectively disabling the integrity check.

Please note that at the time this CVE is issued, the policy mechanism is an experimental feature of Node.js.

Thanks to Tobias Nießen who reported and created the security patch.

— Node.Js

When the Node.js policy feature checks the integrity of a resource against a trusted manifest, the application can intercept the operation and return a forged checksum to node's policy implementation, thus effectively disabling the integrity check.

References: https://nodejs.org/en/blog/vulnerability/october-2023-security-releases

— Red Hat

When the Node.js policy feature checks the integrity of a resource against a trusted manifest, the application can intercept the operation and return a forged checksum to the node's policy implementation, thus effectively disabling the integrity check. Impacts: This vulnerability affects all users using the experimental policy mechanism in all active release lines: 18.x and, 20.x. Please note that at the time this CVE was issued, the policy mechanism is an experimental feature of Node.js.

Affected Software

26 affected componentsFixes available
IBM Cognos Analytics<=12.0.0-12.0.2
IBM Cognos Analytics<=11.2.0-11.2.4 FP3
Nodejs Node.js>=18.0.0<=18.18.1
Nodejs Node.js>=20.1.0<=20.8.0
Fedoraproject Fedora=37
Fedoraproject Fedora=38
Fedoraproject Fedora=39
Node.js Node.js>=18.0.0<18.18.2, >=20.0.0<20.8.1
18.18.220.8.1
Node.js Node.js>=18.0.0<18.18.2
18.18.2
Node.js Node.js>=20.0.0<20.8.1
20.8.1
alpine/nodejs<18.18.2-r0
18.18.2-r0
alpine/nodejs<18.18.2-r0
18.18.2-r0
alpine/nodejs<18.18.2-r0
18.18.2-r0
alpine/nodejs<18.18.2-r0
18.18.2-r0
alpine/nodejs<18.18.2-r0
18.18.2-r0
alpine/nodejs<18.18.2-r0
18.18.2-r0
alpine/nodejs<18.18.2-r0
18.18.2-r0
alpine/nodejs<18.18.2-r0
18.18.2-r0
alpine/nodejs-current<20.8.1-r0
20.8.1-r0
alpine/nodejs-current<20.8.1-r0
20.8.1-r0
alpine/nodejs-current<20.8.1-r0
20.8.1-r0
alpine/nodejs-current<20.8.1-r0
20.8.1-r0
alpine/nodejs-current<20.8.1-r0
20.8.1-r0
alpine/nodejs-current<20.8.1-r0
20.8.1-r0
alpine/nodejs-current<20.8.1-r0
20.8.1-r0
debian/nodejs
18.20.4+dfsg-1~deb12u218.20.4+dfsg-1~deb12u320.19.2+dfsg-1+deb13u220.19.2+dfsg-1+deb13u324.21.0+dfsg+~cs24.13.4-124.22.2+dfsg+~cs24.19.2-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 18.18.2Fixed in 20.8.1
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 18.18.2
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 20.8.1
  4. Upgrade

    Upgrade alpine/nodejs to a version that resolves this vulnerability.

    Fixed in 18.18.2-r0
  5. Upgrade

    Upgrade alpine/nodejs-current to a version that resolves this vulnerability.

    Fixed in 20.8.1-r0
  6. Upgrade

    Upgrade debian/nodejs to a version that resolves this vulnerability.

    Fixed in 18.20.4+dfsg-1~deb12u2Fixed in 18.20.4+dfsg-1~deb12u3Fixed in 20.19.2+dfsg-1+deb13u2Fixed in 20.19.2+dfsg-1+deb13u3Fixed in 24.21.0+dfsg+~cs24.13.4-1Fixed in 24.22.2+dfsg+~cs24.19.2-1

Event History

Oct 13, 2023
CVE Published
via Node.js·01:30 PM
Data Sourced
via Node.js·01:30 PM
DescriptionSeverityAffected Software
Oct 16, 2023
Data Sourced
via Red Hat·12:33 PM
DescriptionSeverityAffected Software
Oct 18, 2023
CVE Published
via MITRE·03:55 AM
Data Sourced
via MITRE·03:55 AM
Description
Data Sourced
via NVD·04:15 AM
DescriptionSeverityWeaknessAffected Software
Data Sourced
04:15 AM
Description
Data Sourced
via OSV·04:15 AM
DescriptionSeverityAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the vulnerability ID?

The vulnerability ID is CVE-2023-38552.

2

What is the severity of CVE-2023-38552?

The severity of CVE-2023-38552 is medium (severity value: 4).

3

How does CVE-2023-38552 affect Node.js?

CVE-2023-38552 affects all users of Node.js.

4

What is the impact of CVE-2023-38552?

The impact of CVE-2023-38552 is that the vulnerability allows an application to disable the integrity check of a resource.

5

Are there any references available for CVE-2023-38552?

Yes, you can find references for CVE-2023-38552 at the following links: [https://hackerone.com/reports/2094235](https://hackerone.com/reports/2094235), [https://nodejs.org/en/blog/vulnerability/october-2023-security-releases](https://nodejs.org/en/blog/vulnerability/october-2023-security-releases), [https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2244472](https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2244472).

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203