CVE-2023-25140
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 V34.0 (All versions < V34.0.254), Parasolid V34.1 (All versions < V34.1.242), Parasolid V35.0 (All versions < V35.0.170), Parasolid V35.1 (All versions < V35.1.150), Solid Edge SE2022 (All versions < V222.0MP12). The affected applications contain an out of bounds read past the end of an allocated structure while parsing specially crafted PAR files. This could allow an attacker to execute code in the context of the current process.
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 confidenceParasolid and Solid Edge contain an out-of-bounds read vulnerability when parsing specially crafted PAR (Parasolid) files. The vulnerability occurs when the parser reads past the end of an allocated memory structure, potentially allowing an attacker to achieve arbitrary code execution 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>= 34.0, < 34.0.254>= 34.1, < 34.1.242>= 35.0, < 35.0.170>= 35.1, < 35.1.150= se2022CVSS 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 if Siemens Parasolid is installedCheck for Parasolid installation directory (typically under Program Files/Siemens) or look for Parasolid-related processes/services. Use 'Get-ItemProperty' in PowerShell for registry keys under HKLM:\SOFTWARE\Siemens\Parasolid or check program files directories.Affected if Parasolid is installed and the version falls within any of these ranges: >=34.0 and <34.0.254, >=34.1 and <34.1.242, >=35.0 and <35.0.170, or >=35.1 and <35.1.150
-
Determine Parasolid version numberLocate the Parasolid executable (typically parasolid.exe or related DLLs in the installation folder) and check its version property via right-click Properties in Windows Explorer, or use PowerShell: (Get-Item 'C:\Program Files\Siemens\Parasolid\<install_dir>\parasolid.exe').VersionInfo.FileVersionAffected if The version number is less than 34.0.254, 34.1.242, 35.0.170, or 35.1.150 depending on the major.minor branch in use
-
Identify if Solid Edge SE2022 is installedCheck for Solid Edge installation under Program Files/Siemens or look for Solid Edge-related executables (e.g., solidedge.exe). Verify the specific version via registry key HKLM:\SOFTWARE\Siemens\SolidEdge\Version or by checking the executable properties.Affected if Solid Edge SE2022 is installed (exact version match = se2022)
-
Determine Solid Edge SE2022 versionIn Solid Edge, go to Help > About Solid Edge to view the version number, or check the executable properties of solidedge.exe in the installation directory.Affected if The installed version is SE2022 (se2022) and is earlier than V222.0MP12
-
Verify PAR file parsing capability is in useCheck if users or automated processes routinely open or import PAR (Parasolid) files within the environment. Search for .par file associations or recent .par file activity in file servers or endpoint detection logs.Affected if PAR file parsing is enabled and users process PAR files with the affected software
The environment is affected if Siemens Parasolid (any version from 34.0 up to but not including 34.0.254, 34.1.242, 35.0.170, or 35.1.150) or Solid Edge SE2022 (versions prior to V222.0MP12) is installed and can process PAR 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 · scoped34.0.25434.1.24235.0.170
Apply vendor-provided patches by updating Parasolid to version V34.0.254, V34.1.242, V35.0.170, or V35.1.150 (or later), and Solid Edge SE2022 to V222.0MP12 or later.
Parasolid: V34.0.254, V34.1.242, V35.0.170, V35.1.150 or later; Solid Edge: V222.0MP12 or later
- Identify the current Parasolid or Solid Edge version installed in your environment
- For Parasolid V34.0.x: upgrade to version 34.0.254 or later
- For Parasolid V34.1.x: upgrade to version 34.1.242 or later
- For Parasolid V35.0.x: upgrade to version 35.0.170 or later
- For Parasolid V35.1.x: upgrade to version 35.1.150 or later
- For Solid Edge SE2022: upgrade to version V222.0MP12 or later
- Obtain the update from the official Siemens support portal (cert-portal.siemens.com)
- Apply the update following standard Siemens installation procedures
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-25140 — 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-25140 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