Отправить #1053804: assimp <= 6.0.5 and master Out-of-bounds WriteИнформация

Названиеassimp <= 6.0.5 and master Out-of-bounds Write
Описаниеassimp: out-of-bounds write in JoinVerticesProcess::ProcessMesh Advisory metadata (GitHub Security Advisory form) field value Ecosystem Other Package name assimp (repository assimp/assimp) Affected versions master up to f936bf18 (2026-09-24) — verified there; <= 6.0.5 Patched versions (none) Severity High (7.0–8.8) CVSS 3.1 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H = 7.0; server-side AV:N/…/UI:N = 8.8 Severity: High — AddressSanitizer classifies the first invalid access as a write (memory corruption), not a plain crash: an attacker-influenced index or length drives a store outside the buffer that owns it. Summary JoinVerticesProcess::ProcessMesh() (part of the post-processing chain for exporters that request aiProcess_JoinIdenticalVertices) compacts a mesh's vertex array and marks which vertices are kept. The bookkeeping write is performed through an index taken from the mesh, without validating it against the buffer that holds the flags, so a crafted model makes the store land outside the buffer: ==1062==ERROR: AddressSanitizer: SEGV on unknown address 0x602017d7f400 (pc 0x5a9b94ca12ee bp 0x7ffed9410970 sp 0x7ffed94107a0 T0) ==1062==The signal is caused by a WRITE memory access. How to reproduce assimp export poc.bin out.stl Both attached samples crash on every run (2/2 each) with the plain build (SIGSEGV) and with the ASan build. Sanitizer stack #0 0x5a9b94ca12ee in std::_Bit_reference::operator=(bool) /usr/bin/../lib/gcc/x86_64-linux-gnu/12/../../../../include/c++/12/bits/stl_bvector.h:103:8 #1 0x5a9b94ca12ee in Assimp::JoinVerticesProcess::ProcessMesh(aiMesh*, unsigned int) /home/dell/data1/czh/projects/2026/fogfuzz/.scratch/newfmt/assimp-git/code/PostProcessing/JoinVerticesProcess.cpp:242:53 #2 0x5a9b94ca09eb in Assimp::JoinVerticesProcess::Execute(aiScene*) /home/dell/data1/czh/projects/2026/fogfuzz/.scratch/newfmt/assimp-git/code/PostProcessing/JoinVerticesProcess.cpp:82:25 Suggested fix Range-check the vertex index against the size of the flag/buffer before writing, and allocate the bookkeeping arrays from the validated (mNumVertices) count. Impact Converting an untrusted model triggers an out-of-bounds write (heap corruption): denial of service and a plausible exploitation primitive. Attachments seeds/id:000436,sig:11,src:000150,time:10618136,execs:1879763,op:havoc,rep:2 — crashes every run seeds/id:000453,sig:11,src:000150,time:10065197,execs:1856753,op:havoc,rep:3 — crashes every run asan/assimp-joinverticesprocess-242-asan.txt — AddressSanitizer report (invalid write) Samples are unmodified AFL++ test cases with their original file names. Plain-build verification (rules out sanitizer-layout artifacts) The same input was replayed against the plain (non-sanitizer) release build of the same source tree: condition result plain build, repeated -11, -11, -11, -11, -11 (SIGSEGV) — consistent every run MALLOC_CHECK_=3 (glibc heap consistency checks) -11 ASLR disabled (setarch -R) -11 The process dies from a real signal in a normal build, and glibc's heap checks also abort on the corrupted heap, so the report above is not an artifact of AddressSanitizer redzones, allocator layout or instrumentation.
Источник⚠️ https://github.com/PassMoon/CVE-application/tree/main/assimp-4-joinvertices-oob-write
Пользователь
 Anonymous User
Представление23.10.2026 10:49 (1 месяц назад)
Модерация22.11.2026 17:21 (1 month later)
Статуспринято
Запись VulDB442131 [Open Asset Import Library Assimp до 6.0.6 PostProcessing JoinVerticesProcess JoinVerticesProcess.cpp ProcessMesh повреждение памяти]
Баллы20

Interested in the pricing of exploits?

See the underground prices here!