Code execution via unchecked VC6 buffer write
Published Mar 11, 2025 · Updated Mar 12, 2025
Out-of-bounds write in Cobalt 1204.91 allows remote attackers to execute code by inducing a user to open a crafted VC6 file. The VC6 parser fails to validate user-supplied data before writing it beyond the end of an allocated buffer. Exploitation requires user interaction, and successful execution runs attacker-controlled code in the context of the current Cobalt process.
Summary
What happened
Out-of-bounds write in Cobalt 1204.91 allows remote attackers to execute code by inducing a user to open a crafted VC6 file. The VC6 parser fails to validate user-supplied data before writing it beyond the end of an allocated buffer. Exploitation requires user interaction, and successful execution runs attacker-controlled code in the context of the current Cobalt process.
The record
- CVE
- CVE-2025-2020
- Published
- Mar 11, 2025
- Updated
- Mar 12, 2025
- Vendor
- Ashlar-Vellum
- Product
- Cobalt
- Classifications
- CWE-787, T1203, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 11, 2025CVE publishedPublication date reported by the CVE source.
- Mar 12, 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=1204.91
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