CVE-2021-46157
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability has been identified in Simcenter Femap V2020.2 (All versions), Simcenter Femap V2021.1 (All versions). Affected application contains a memory corruption vulnerability while parsing NEU files. This could allow an attacker to execute code in the context of the current process. (ZDI-CAN-14757)
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceMemory corruption vulnerability in Simcenter Femap when parsing NEU (Neutral) files. The vulnerability occurs during file parsing operations and can allow an attacker to achieve code execution within the context of the running process. This is a classic file-based memory corruption (likely buffer overflow) vulnerability triggered by malformed NEU input.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 2020.2= 2021.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Simcenter Femap versionOpen Femap and navigate to Help > About Simcenter Femap, or check the program's file properties (right-click femap.exe > Properties > Details). The version is displayed as a 4-digit number such as 2020.2 or 2021.1.Affected if The installed version matches exactly 2020.2 or 2021.1
-
Confirm NEU file parsing capability is presentVerify the Femap installation includes the NEU file import module. Check the program installation directory for neuimport.dll or similar NEU-related DLL files.Affected if NEU parsing modules exist in the Femap installation directory
-
Review recent file import activityCheck the Femap working directory or recent documents for .neu files that have been opened. On Windows, check recent files via File > Recent or examine the application log files if logging is enabled.Affected if The user has recently opened .neu files in Femap
-
Check for crash logs or error reportsSearch the Windows Event Viewer Application logs for Femap-related crash events, or check the Femap log directory for error entries mentioning 'NEU' or 'neutral' file parsing failures.Affected if Crashes or errors are logged related to NEU file parsing operations
A user is affected if Simcenter Femap version 2020.2 or 2021.1 is installed AND the NEU file parsing feature is used to open untrusted .neu files.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply vendor patches when released by Siemens. Until then, implement controls to prevent opening untrusted NEU files - restrict file来源 and validate NEU files before processing in Femap.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-46157 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-46157 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data