Process crash via unchecked MDL frame bounds
Published May 26, 2025 · Updated May 28, 2025
Out-of-bounds read in Assimp 5.4.3 allows local users to crash an importing process by supplying a malformed Quake 1 MDL file. MDLImporter::InternReadFile_Quake1 dereferences frame metadata and calculates a grouped-frame pointer before validating that the input contains those structures. The vulnerable process must import the crafted file; published sanitizer runs terminate on the invalid heap read, causing a process crash.
Summary
What happened
Out-of-bounds read in Assimp 5.4.3 allows local users to crash an importing process by supplying a malformed Quake 1 MDL file. MDLImporter::InternReadFile_Quake1 dereferences frame metadata and calculates a grouped-frame pointer before validating that the input contains those structures. The vulnerable process must import the crafted file; published sanitizer runs terminate on the invalid heap read, causing a process crash.
The record
- CVE
- CVE-2025-5200
- Published
- May 26, 2025
- Updated
- May 28, 2025
- Vendor
- Open Asset Import Library
- Product
- Assimp
- Classifications
- CWE-119, CWE-125
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 26, 2025CVE publishedPublication date reported by the CVE source.
- May 28, 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=5.4.3
What conditions does exploitation require?
What is affected?
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
- Assimp MDL line-452 reproducerproof 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