CVE-2023-39333: Code injection via WebAssembly export names

Published Oct 13, 2023
·
Updated

Code injection via WebAssembly export names (Low)

Other sources

Maliciously crafted export names in an imported WebAssembly module can inject JavaScript code. The injected code may be able to access data and functions that the WebAssembly module itself does not have access to, similar to as if the WebAssembly module was a JavaScript module.

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

— Red Hat

Maliciously crafted export names in an imported WebAssembly module can inject JavaScript code. The injected code may be able to access data and functions that the WebAssembly module itself does not have access to, similar to as if the WebAssembly module was a JavaScript module.

Thanks to dittyroma for reporting the issue and to Tobias Nießen for fixing it.

— Node.Js

Maliciously crafted export names in an imported WebAssembly module can inject JavaScript code. The injected code may be able to access data and functions that the WebAssembly module itself does not have access to, similar to as if the WebAssembly module was a JavaScript module.

This vulnerability affects users of any active release line of Node.js. The vulnerable feature is only available if Node.js is started with the --experimental-wasm-modules command line option.

— MITRE

Node.js could allow a remote attacker to gain unauthorized access to the system, caused by a code injection flaw. By using specially crafted export names in an imported WebAssembly module, an attacker could exploit this vulnerability to inject JavaScript code and gain access to restricted data and functions.

— IBM

Affected Software

21 affected componentsFixes available
IBM Cognos Analytics<=12.0.0-12.0.2
IBM Cognos Analytics<=11.2.0-11.2.4 FP3
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:46 PM
DescriptionSeverityAffected Software
Sep 7, 2024
CVE Published
via MITRE·04:00 PM
Data Sourced
via MITRE·04:00 PM
Description
Data Sourced
via NVD·04:15 PM
DescriptionSeverityWeakness
Data Sourced
via OSV·04:15 PM
DescriptionSeverityAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the severity of CVE-2023-39333?

CVE-2023-39333 has been classified as a critical vulnerability due to its potential for remote code execution.

2

How do I fix CVE-2023-39333?

To fix CVE-2023-39333, apply the available patches provided by IBM for affected versions of Cognos Analytics.

3

Which versions of IBM Cognos Analytics are affected by CVE-2023-39333?

CVE-2023-39333 affects IBM Cognos Analytics versions up to 12.0.2 and 11.2.4 FP3.

4

What is the nature of the vulnerability in CVE-2023-39333?

CVE-2023-39333 allows maliciously crafted WebAssembly exports to inject JavaScript code into the application.

5

Can CVE-2023-39333 lead to data breaches?

Yes, CVE-2023-39333 could potentially lead to data breaches by allowing unauthorized access to sensitive data and functions.

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