Code execution via unchecked CO file length
Published May 3, 2024 · Updated Sep 18, 2024
Heap-based buffer overflow in the CO file parser in Ashlar-Vellum Cobalt 11 build 1111 allows attackers to execute code via a crafted CO file. The parser copies user-supplied data into a heap buffer without validating its length, allowing the copy to overrun the allocation. Exploitation requires a person to visit a malicious page or open a malicious file, after which code runs with the current process's privileges.
Summary
What happened
Heap-based buffer overflow in the CO file parser in Ashlar-Vellum Cobalt 11 build 1111 allows attackers to execute code via a crafted CO file. The parser copies user-supplied data into a heap buffer without validating its length, allowing the copy to overrun the allocation. Exploitation requires a person to visit a malicious page or open a malicious file, after which code runs with the current process's privileges.
The record
- CVE
- CVE-2023-34299
- Published
- May 3, 2024
- Updated
- Sep 18, 2024
- Vendor
- Ashlar-Vellum
- Product
- Cobalt
- Classifications
- CWE-122, T1203, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 3, 2024CVE publishedPublication date reported by the CVE source.
- Sep 18, 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=*
- Affected versionversion=Ashlar-Vellum Cobalt 11 build 1111
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