CVE-2024-36138: Bypass incomplete fix of CVE-2024-27980

Published Jul 8, 2024
·
Updated

Bypass incomplete fix of CVE-2024-27980, that arises from improper handling of batch files with all possible extensions on Windows via childprocess.spawn / childprocess.spawnSync. A malicious command line argument can inject arbitrary commands and achieve code execution even if the shell option is not enabled.

Other sources

Node.js could allow a remote attacker to execute arbitrary commands on the system, caused by the incomplete fix of CVE-2024-27980 which was the improper handling of batch files in childprocess.spawn / childprocess.spawnSync. By sending a specially crafted command line argument, an attacker could exploit this vulnerability to inject and execute arbitrary commands on the system.

— IBM

The CVE-2024-27980 was identified as an incomplete fix for the BatBadBut vulnerability. This vulnerability arises from improper handling of batch files with all possible extensions on Windows via childprocess.spawn / childprocess.spawnSync. A malicious command line argument can inject arbitrary commands and achieve code execution even if the shell option is not enabled.

This vulnerability affects all users of childprocess.spawn and childprocess.spawnSync on Windows in all active release lines.

— Node.Js

The CVE-2024-27980 was identified as an incomplete fix for the BatBadBut vulnerability. This vulnerability arises from improper handling of batch files with all possible extensions on Windows via childprocess.spawn / childprocess.spawnSync. A malicious command line argument can inject arbitrary commands and achieve code execution even if the shell option is not enabled.

— Node.Js

Affected Software

7 affected componentsFixes available
IBM Controller<=11.1.0
IBM Controller<=11.0.0 - 11.0.1
All of the following
Node.js Node.js>=18.0.0<18.20.4, >=20.0.0<20.15.1, >=22.0.0<22.4.1
18.20.420.15.122.4.1
Microsoft Windows*
Node.js Node.js>=18.0.0<18.20.4
18.20.4
Node.js Node.js>=20.0.0<20.15.1
20.15.1
Node.js Node.js>=22.0.0<22.4.1
22.4.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.20.4Fixed in 20.15.1Fixed in 22.4.1
  2. Upgrade

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

    Fixed in 18.20.4
  3. Upgrade

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

    Fixed in 20.15.1
  4. Upgrade

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

    Fixed in 22.4.1

Event History

Jul 8, 2024
CVE Published
via Node.js·03:00 AM
Data Sourced
via Node.js·03:00 AM
DescriptionSeverityAffected Software
Sep 7, 2024
CVE Published
via MITRE·04:00 PM
Data Sourced
via MITRE·04:00 PM
DescriptionSeverity
Data Sourced
via NVD·04:15 PM
DescriptionSeverityWeakness
Feb 28, 2025
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2024-36138?

CVE-2024-36138 is classified as a high-severity vulnerability due to the potential for arbitrary code execution.

2

How do I fix CVE-2024-36138?

To mitigate CVE-2024-36138, update to IBM Planning Analytics versions beyond 2.1 or 2.0, which contain the patched code.

3

What software is affected by CVE-2024-36138?

CVE-2024-36138 affects IBM Planning Analytics versions 2.1 and 2.0.

4

What type of vulnerability is CVE-2024-36138?

CVE-2024-36138 is a command injection vulnerability that allows attackers to execute arbitrary commands.

5

What was the cause of CVE-2024-36138?

The vulnerability was caused by improper handling of batch files through the child_process.spawn method in Node.js.

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