Code execution via oversized UPK byte array
Published May 18, 2021 · Updated Aug 3, 2024
Stack-based buffer overflow in Rocket League 1.95 and earlier allows attackers to execute code through a crafted UPK file. The UPK parser fails to bound a large byte array placed near the file's magic header, overrunning the stack in AK::MemoryMgr::GetPoolName. The published scenario requires user interaction and administrator-level payload placement in CookedPCConsole; the demonstrated artifact crashes the game, while weaponized code execution was not shown.
Summary
What happened
Stack-based buffer overflow in Rocket League 1.95 and earlier allows attackers to execute code through a crafted UPK file. The UPK parser fails to bound a large byte array placed near the file's magic header, overrunning the stack in AK::MemoryMgr::GetPoolName. The published scenario requires user interaction and administrator-level payload placement in CookedPCConsole; the demonstrated artifact crashes the game, while weaponized code execution was not shown.
The record
- CVE
- CVE-2021-32238
- Published
- May 18, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002, T1203
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- May 18, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- rocketleague_bof.txt proof of conceptproof of concept · demonstrated
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