Security readout for executives and security teams
Plain-English summary
This vulnerability affects Siemens Simcenter Femap V2020.2 and V2021.1 when handling specially crafted NEU files. If a user opens a malicious file, the application may write outside expected memory and allow code execution as that user. Business risk is highest where engineering teams exchange NEU files externally.
Executive priority
Treat this as a targeted workstation risk for engineering environments. Prioritize affected Femap users who handle external model files before broad enterprise action.
Technical view
CVE-2021-46156 is a CWE-787 out-of-bounds write in Simcenter Femap NEU file parsing. The issue is described as writing past an allocated structure, potentially enabling code execution in the current process. The provided bundle names ZDI-CAN-14684 and affected Siemens versions only.
Likely exposure
Exposure is likely limited to organizations running Simcenter Femap V2020.2 or V2021.1, especially workstations that open NEU files from suppliers, customers, or shared engineering repositories.
Exploitation context
The sources describe maliciously crafted NEU files as the trigger. There is no KEV listing and no provided source evidence of active exploitation in the wild.
Researcher notes
The bundle lacks CVSS data, exploit status, and explicit remediation detail. Analysis is based on the CVE description, affected versions, CWE-787 classification, Siemens advisory reference, and ZDI advisory reference.
Mitigation direction
- Inventory Simcenter Femap V2020.2 and V2021.1 installations.
- Review Siemens SSA-609880 for vendor-supported updates or workarounds.
- Limit opening NEU files from untrusted or external sources.
- Use isolated workstations for externally supplied engineering files.
- Prioritize controls for users handling supplier or customer NEU files.
Validation and detection
- Confirm whether affected Femap versions exist in software inventory.
- Identify teams that routinely exchange or import NEU files.
- Review endpoint telemetry for Femap crashes after opening NEU files.
- Check whether external NEU files are scanned or quarantined before use.
- Verify Siemens advisory guidance has been applied where relevant.
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.
CWE-787: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2021-46156 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://cert-portal.siemens.com/productcert/pdf/ssa-609880.pdfCVE reference · x_refsource_MISC
- https://www.zerodayinitiative.com/advisories/ZDI-22-309/CVE reference · x_refsource_MISC
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.
Out-of-bounds Write
Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.