Code execution via SSD object use-after-free
Published Jan 25, 2021 · Updated Aug 3, 2024
Use-after-free in EcoStruxure Power Build - Rapsody 2.1.13 and earlier allows remote attackers to execute code via a malicious SSD file. The SSD parser performs operations on an object without first validating that the object still exists, leaving a stale object reference during file processing. Exploitation requires a target to open the attacker-supplied file or visit malicious content, and successful code runs in the current process.
Summary
What happened
Use-after-free in EcoStruxure Power Build - Rapsody 2.1.13 and earlier allows remote attackers to execute code via a malicious SSD file. The SSD parser performs operations on an object without first validating that the object still exists, leaving a stale object reference during file processing. Exploitation requires a target to open the attacker-supplied file or visit malicious content, and successful code runs in the current process.
The record
- CVE
- CVE-2021-22697
- Published
- Jan 25, 2021
- Updated
- Aug 3, 2024
- Vendor
- Distributed Data Systems
- Product
- EcoStruxure Power Build - Rapsody
- Classifications
- CWE-434, T1203, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 25, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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=EcoStruxure Power Build - Rapsody software V2.1.13 and prior.
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