Authenticated command execution via crafted YAML deserialization
Published Sep 26, 2024 · Updated Sep 26, 2024
Deserialization of untrusted YAML in IBM Cloud Pak for Multicloud Management 2.3 through 2.3 FP8 allows remote authenticated users to execute commands. IBM identifies the vulnerable locus only as ManageIQ's handling of crafted YAML file requests and has not published the affected function or deserialization path. Administrative access to the network-reachable interface is required, and successful exploitation grants command execution in the service context.
Summary
What happened
Deserialization of untrusted YAML in IBM Cloud Pak for Multicloud Management 2.3 through 2.3 FP8 allows remote authenticated users to execute commands. IBM identifies the vulnerable locus only as ManageIQ's handling of crafted YAML file requests and has not published the affected function or deserialization path. Administrative access to the network-reachable interface is required, and successful exploitation grants command execution in the service context.
The record
- CVE
- CVE-2024-43191
- Published
- Sep 26, 2024
- Updated
- Sep 26, 2024
- Vendor
- IBM
- Product
- IBM Cloud Pak for Multicloud Management
- Classifications
- CWE-502, T1059
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Sep 26, 2024CVE publishedPublication date reported by the CVE source.
- Sep 26, 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=2.3, 2.3 FP8
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
No public exploit references are available in this record.
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