CVE-2023-41033
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 Parasolid V35.0 (All versions < V35.0.260), Parasolid V35.1 (All versions < V35.1.246), Parasolid V36.0 (All versions < V36.0.156), Simcenter Femap V2301 (All versions < V2301.0003), Simcenter Femap V2306 (All versions < V2306.0001). The affected application contains an out of bounds write past the end of an allocated structure while parsing specially crafted X_T files. This could allow an attacker to execute code in the context of the current process. (ZDI-CAN-21266)
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 confidenceAn out-of-bounds write vulnerability exists in Parasolid and Simcenter Femap when parsing X_T files. The application writes past the end of an allocated buffer during parsing of specially crafted files, allowing an attacker to execute arbitrary code in the context of the current process.
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>= 35.0, < 35.0.260>= 35.1, < 35.1.246>= 36.0, < 36.0.156>= 2301.0, < 2301.0003>= 2306.0, < 2306.0001CVSS 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 Siemens productCheck if Siemens Parasolid or Simcenter Femap is installed. Look for executable files such as 'parasolid.exe', 'femap.exe', or check installed programs in Windows Control Panel or registry under HKLM\SOFTWARE\Siemens. Product may also be embedded in other Siemens software.Affected if Either Parasolid or Simcenter Femap is installed
-
Determine Parasolid versionFor Parasolid, check the file properties of the main executable (often in program files), or query via the application's 'About' dialog. The version format is like 35.0.x or 36.0.x.Affected if Parasolid version is 35.0.x where x < 260, OR 35.1.x where x < 246, OR 36.0.x where x < 156
-
Determine Simcenter Femap versionFor Simcenter Femap, check the file properties of 'femap.exe' or use the application's Help > About dialog. Version format is 2301.x or 2306.x.Affected if Simcenter Femap version is 2301.0.x where x < 0003, OR 2306.0.x where x < 0001
-
Check for X_T file handling capabilityVerify the application can parse X_T files. This is a native Parasolid format. The vulnerability triggers when opening a specially crafted .x_t file. Check recent file access logs or the application's file open dialog to see if X_T is a supported format.Affected if X_T file parsing is enabled and the application can open .x_t files
Environment is affected if either Parasolid (version 35.0.x below 260, 35.1.x below 246, or 36.0.x below 156) or Simcenter Femap (version 2301.0.x below 0003 or 2306.0.x below 0001) is installed AND the application can process X_T 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.
dbcve · scoped35.0.26035.1.24636.0.156
Apply vendor patches to reach V35.0.260, V35.1.246, V36.0.156, V2301.0003, or V2306.0001 respectively, and avoid opening untrusted X_T files from unknown or untrusted sources.
Parasolid V35.0.260, V35.1.246, or V36.0.156; Simcenter Femap V2301.0003 or V2306.0001
- 1. Identify the currently installed Parasolid or Simcenter Femap version by checking the application's About or Help menu
- 2. Determine which product line and version family applies to your installation (Parasolid V35.0, V35.1, or V36.0; or Simcenter Femap V2301 or V2306)
- 3. Download the corresponding fixed version from the Siemens support portal or your licensed software distribution channel: Parasolid V35.0.260, V35.1.246, or V36.0.156; or Simcenter Femap V2301.0003 or V2306.0001
- 4. Back up all critical data and custom configurations before upgrading
- 5. Install the fixed version following standard Siemens installation procedures
- 6. Validate the installation by confirming the updated version number in the application
- 7. Test parsing of X_T files to confirm the vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-41033 — 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-2023-41033 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