Executive Summary

This vulnerability is a heap-use-after-free flaw in the Open Asset Import Library (Assimp) up to version 6.0.2, specifically in the function Assimp::LWOImporter::FindUVChannels within LWOMaterial.cpp. It occurs when processing specially crafted LWO (LightWave Object) files, where the program accesses memory that has already been freed due to improper management of a std::vector<bool> container used for UV channel data. This leads to undefined behavior such as crashes or potential arbitrary code execution when the vulnerable function attempts to read from the freed memory. [2, 3, 4]

Useful 0 Not Useful 0

Impact Analysis

This vulnerability can cause the affected application to crash or behave unexpectedly when processing maliciously crafted LWO files. It may also allow an attacker with local access to execute arbitrary code, compromising the confidentiality, integrity, and availability of the system using the Assimp library for 3D model importing. The exploit has been publicly disclosed and is considered easy to exploit locally, leading to denial of service or potential code execution. [2, 3, 4]

Useful 0 Not Useful 0

Detection Guidance

This vulnerability can be detected by reproducing the issue using the publicly available proof-of-concept exploit. Detection involves compiling the Assimp library with AddressSanitizer enabled and running the `assimp extract` command on a crafted malicious LWO file (such as the provided `assimp_poc10`). The AddressSanitizer will report heap-use-after-free errors during this process. Suggested commands include cloning the Assimp repository, checking out the specific commit, compiling with Clang and AddressSanitizer (`-fsanitize=address`), and executing: `assimp extract assimp_poc10` to trigger the detection. [2]

Useful 0 Not Useful 0

Mitigation Strategies

Immediate mitigation steps include avoiding processing untrusted or malicious LWO files with the affected Assimp versions up to 6.0.2. Since no known mitigations or patches currently exist, it is recommended to consider replacing the affected Assimp library with an alternative or updated version once available. Restrict local access to systems running vulnerable versions to prevent exploitation, as the attack requires local access. [4]

Useful 0 Not Useful 0