Security readout for executives and security teams
Plain-English summary
Assimp 5.1.0 and 5.1.1 have a heap-based buffer overflow while handling M3D model data. Business risk depends on whether your software imports untrusted 3D assets. The source bundle does not provide a CVSS score, confirmed exploitation, or a specific fixed version.
Executive priority
Treat this as dependency exposure requiring targeted inventory, not an organization-wide emergency. Raise priority if customer-uploaded or partner-supplied 3D files reach assimp parsing paths.
Technical view
CVE-2021-45948 affects Open Asset Import Library (assimp) 5.1.0 and 5.1.1. The flaw is in _m3d_safestr, called from m3d_load and Assimp::M3DWrapper::M3DWrapper, and is described as a heap-based buffer overflow during M3D parsing.
Likely exposure
Exposure is most likely in applications, services, or build pipelines that use assimp 5.1.0 or 5.1.1 to process M3D or other imported 3D assets, especially from external users or suppliers.
Exploitation context
The bundle cites OSS-Fuzz and Chromium issue tracking, which suggests the flaw was found through fuzzing. It is not listed as KEV, and the provided sources do not state active exploitation.
Researcher notes
Key missing data includes CVSS, CWE, detailed affected CPEs, and explicit fixed version in the supplied bundle. Analysis should stay constrained to assimp 5.1.0/5.1.1 and the M3D parser call chain named in the CVE description.
Mitigation direction
- Inventory assimp usage across applications, containers, and build systems.
- Check Assimp upstream and Gentoo GLSA-202210-01 for vendor remediation guidance.
- Prioritize systems that process externally supplied 3D model files.
- Restrict or disable untrusted M3D imports until remediation is confirmed.
- Document any compensating controls for exposed asset-processing workflows.
Validation and detection
- Confirm whether assimp 5.1.0 or 5.1.1 is present.
- Map which workflows parse M3D or user-supplied 3D assets.
- Verify remediation against vendor guidance, not only package names.
- Review crash telemetry for assimp M3D parser faults.
- Track the CVE record for updated scoring or fix details.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2021-45948 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/google/oss-fuzz-vulns/blob/main/vulns/assimp/OSV-2021-775.yamlCVE reference
- https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=34416CVE reference
- GLSA-202210-01CVE reference · vendor-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.