Local command execution via shell-enabled subprocess
Published Mar 26, 2024 · Updated Aug 5, 2024
OS command injection in Ansys PyAnsys Geometry 0.3.0 through 0.3.2 and 0.4.0 through 0.4.11 allows local users to execute commands. The _start_program function passes its caller-controlled argument list to subprocess.Popen with shell=True on non-Windows systems, allowing shell metacharacters to alter the intended command. Exploitation requires local Python access and a direct call to this internal method; resulting commands run with the script's privileges.
Summary
What happened
OS command injection in Ansys PyAnsys Geometry 0.3.0 through 0.3.2 and 0.4.0 through 0.4.11 allows local users to execute commands. The _start_program function passes its caller-controlled argument list to subprocess.Popen with shell=True on non-Windows systems, allowing shell metacharacters to alter the intended command. Exploitation requires local Python access and a direct call to this internal method; resulting commands run with the script's privileges.
The record
- CVE
- CVE-2024-29189
- Published
- Mar 26, 2024
- Updated
- Aug 5, 2024
- Vendor
- Ansys
- Product
- PyAnsys Geometry
- Classifications
- CWE-78, T1059
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 26, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 0.3.0, < 0.3.3
- Affected versionversion=0.3.0 <0.3.3
- Affected versionversion=>= 0.4.0, < 0.4.12
- Affected versionversion=0.4.0 <0.4.12
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Direct _start_program invocation proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo