Heap corruption via unbounded CSM node-name copy
Published Mar 21, 2025 · Updated Mar 21, 2025
Heap-based buffer overflow in Assimp 5.4.3 allows attackers to corrupt heap memory by importing a malformed CSM file. CSMImporter::InternReadFile copies bytes into mNodeName.data until whitespace, but its loop fails to stop at the end of the CSM input buffer. A consuming application must import the crafted file; the demonstrated result is a one-byte heap overwrite, while code execution remains unproven.
Summary
What happened
Heap-based buffer overflow in Assimp 5.4.3 allows attackers to corrupt heap memory by importing a malformed CSM file. CSMImporter::InternReadFile copies bytes into mNodeName.data until whitespace, but its loop fails to stop at the end of the CSM input buffer. A consuming application must import the crafted file; the demonstrated result is a one-byte heap overwrite, while code execution remains unproven.
The record
- CVE
- CVE-2025-2592
- Published
- Mar 21, 2025
- Updated
- Mar 21, 2025
- Vendor
- Open Asset Import Library
- Product
- Assimp
- Classifications
- CWE-122, CWE-119, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 21, 2025CVE publishedPublication date reported by the CVE source.
- Mar 21, 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
- Malformed CSM file 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