Code execution via malformed XE file parsing
Published Feb 4, 2025 · Updated Feb 5, 2025
Out-of-bounds write in Ashlar-Vellum Cobalt before v12 SP2 Build (1204.200) allows attackers to execute code via a crafted XE file. The XE-file parser fails to validate user-supplied data before writing beyond the intended memory buffer. The same affected range applies to Cobalt Share, Xenon, Argon, and Lithium; exploitation requires a user to open a malicious XE file, and code runs in the current process.
Summary
What happened
Out-of-bounds write in Ashlar-Vellum Cobalt before v12 SP2 Build (1204.200) allows attackers to execute code via a crafted XE file. The XE-file parser fails to validate user-supplied data before writing beyond the intended memory buffer. The same affected range applies to Cobalt Share, Xenon, Argon, and Lithium; exploitation requires a user to open a malicious XE file, and code runs in the current process.
The record
- CVE
- CVE-2023-39943
- Published
- Feb 4, 2025
- Updated
- Feb 5, 2025
- Vendor
- Ashlar-Vellum
- Product
- Cobalt
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 4, 2025CVE publishedPublication date reported by the CVE source.
- Feb 5, 2025Record 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 <v12 SP2 Build (1204.200)
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.
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