Map compiler crash via oversized shader image name
Published Jul 14, 2022 · Updated Aug 3, 2024
Buffer overflow in q3map2 in GtkRadiant 1.6.6 allows attackers to crash the map compiler via a crafted MAP file. During MAP parsing, ParseBrush passes an oversized shader image name to sprintf or strcpy without bounding it to the 64-byte destination. The user must run q3map2 on the malicious file; the demonstrated consequence is process termination, not code execution or data exposure.
Summary
What happened
Buffer overflow in q3map2 in GtkRadiant 1.6.6 allows attackers to crash the map compiler via a crafted MAP file. During MAP parsing, ParseBrush passes an oversized shader image name to sprintf or strcpy without bounding it to the 64-byte destination. The user must run q3map2 on the malicious file; the demonstrated consequence is process termination, not code execution or data exposure.
The record
- CVE
- CVE-2022-32406
- Published
- Jul 14, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 14, 2022CVE 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
- Malformed MAP crash proofproof 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