Code execution via unchecked snprintf return length
Published Jun 12, 2025 · Updated Jun 13, 2025
Stack-based buffer overflow in PCSX2 before 2.3.414 allows context-dependent attackers to execute code through a crafted disc image. Kprintf_HLE uses snprintf's would-have-written length to advance within a fixed stack buffer after truncation, allowing subsequent formatting to write beyond its end. Exploitation requires a user to open the image with IOP Console Logging enabled; successful corruption permits code execution in the PCSX2 process.
Summary
What happened
Stack-based buffer overflow in PCSX2 before 2.3.414 allows context-dependent attackers to execute code through a crafted disc image. Kprintf_HLE uses snprintf's would-have-written length to advance within a fixed stack buffer after truncation, allowing subsequent formatting to write beyond its end. Exploitation requires a user to open the image with IOP Console Logging enabled; successful corruption permits code execution in the PCSX2 process.
The record
- CVE
- CVE-2025-49589
- Published
- Jun 12, 2025
- Updated
- Jun 13, 2025
- Vendor
- PCSX2
- Product
- PCSX2
- Classifications
- CWE-121, T1203
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 12, 2025CVE publishedPublication date reported by the CVE source.
- Jun 13, 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=< 2.3.414
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