CVE-2024-48425: Classic Buffer Overflow
Source CVE Database V5
Not known to be exploited · CVSS 5.5 Medium.
Data as of 26 Oct 2026, 12:54 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 24 Oct 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
- Monitor the Assimp project repositories and security advisories closely for official patches or updates addressing CVE-2024-48425 and apply them promptly once available.
- Until patches are released, consider isolating or sandboxing applications that use Assimp to limit the impact of potential crashes and prevent cascading failures.
- Conduct code reviews and static analysis on the usage of Assimp within your software to identify and mitigate unsafe calls or inputs that might trigger the vulnerability.
- Implement input validation and sanitization for 3D mesh data before processing with Assimp to reduce the likelihood of malformed data causing crashes.
- Restrict local access to systems running vulnerable versions of Assimp to trusted users only, minimizing the risk of exploitation by low-privilege attackers.
- If feasible, consider using alternative 3D asset processing libraries or tools that do not exhibit this vulnerability until a fix is available.
- Employ runtime monitoring and crash detection mechanisms to quickly identify and respond to any exploitation attempts or unexpected application failures related to this issue.
Description
A segmentation fault (SEGV) was detected in the Assimp::SplitLargeMeshesProcess_Triangle::UpdateNode function within the Assimp library during fuzz testing using AddressSanitizer. The crash occurs due to a read access violation at address 0x000000000460, which points to the zero page, indicating a null or invalid pointer dereference.