Technical impact
Assimp versions up to 6.0.6 suffer a heap out‑of‑bounds read in the MD2 file importer. The vulnerability is triggered when the Importer reads the stored frameSize header without validating it, allowing an attacker to read memory beyond the intended buffer. This flaw can cause the application to crash or reveal adjacent heap contents, potentially exposing sensitive data or disrupting normal operation.
Affected Systems
Any deployment of the Assimp 3D asset import library up to and including version 6.0.6 is affected. The flaw exists in the MD2Importer component, which is invoked when an .md2 file is loaded. Systems such as game engines, model viewers, or other applications that rely on Assimp for 3D asset import are at risk if they use the unpatched library.
Risk and Exploitability
The CVSS score of 5.8 indicates a moderate severity. The EPSS score is not available, and the vulnerability is not listed in CISA’s KEV catalog, implying that widespread exploitation is not yet documented. Attackers would need to supply a crafted .md2 file to the target application; if the file is processed automatically (e.g., from a shared directory or a network location), the exploit could be triggered without user interaction. Because the flaw results in an out‑of‑bounds read rather than code execution, the impact is limited to crashing the host process or leaking nearby memory, but it can still cause denial of service or data exposure in sensitive contexts.
