dbcve.org
ParasolidApplication · Siemens

CVE-2022-46346

HIGH · 7.8 CVSS v3.1 Published 2022-12-13
Fix available
A fix is available. Upgrade to 33.1.264 / 34.0.252 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
A vulnerability has been identified in Parasolid V33.1 (All versions < V33.1.264), Parasolid V34.0 (All versions < V34.0.252), Parasolid V34.1 (All versions < V34.1.242), Parasolid V35.0 (All versions < V35.0.170), Solid Edge SE2022 (All versions < V222.0MP12), Solid Edge SE2022 (All versions), Solid Edge SE2023 (All versions < V223.0Update2). The affected applications contain an out of bounds write past the end of an allocated structure while parsing specially crafted X_B files. This could allow an attacker to execute code in the context of the current process. (ZDI-CAN-19071)

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 confidence

Out of bounds write vulnerability in Parasolid and Solid Edge CAD software when parsing specially crafted X_B files. The vulnerability occurs when parsing the X_B file format, allowing an attacker to write past the end of an allocated memory structure and potentially execute arbitrary code in the context of the current process.

MitigationUpdate to the patched versions: Parasolid V33.1.264+, V34.0.252+, V34.1.242+, V35.0.170+, Solid Edge V222.0MP12+, or V223.0Update2+. Avoid opening untrusted X_B files from unknown sources as an interim measure.

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
ParasolidApplication
Affected:>= 33.1, < 33.1.264>= 34.0, < 34.0.252>= 34.1, < 34.1.242>= 35.0, < 35.0.170
Solid Edge Se2022Web browser
Affected:all versions
Solid Edge Se2023Web browser
Affected:all versions= 223.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Parasolid component is installed
    Check for Parasolid installation by examining common installation paths such as C:\Program Files\Siemens\Parasolid or look for Parasolid-related DLLs (xpcd_*.dll) in application directories. The version can often be found in the DLL file properties or in the application's about/info dialog.
    Affected if Parasolid version falls within any of these ranges: >= 33.1.0 and < 33.1.264, >= 34.0.0 and < 34.0.252, >= 34.1.0 and < 34.1.242, >= 35.0.0 and < 35.0.170
  2. Identify if Solid Edge is installed
    Check for Solid Edge installation in typical paths such as C:\Program Files\Siemens\Solid Edge or look for the Solid Edge executable (SolidEdge.exe) on the system.
    Affected if Solid Edge Se2022 (any version) or Solid Edge Se2023 (any version including 223.0) is installed
  3. Determine the installed Parasolid version number
    Locate the Parasolid version through the host application's About dialog, or check the Parasolid DLL file version properties (typically found in the application's bin folder or a Parasolid subfolder). Compare the version string against the affected ranges.
    Affected if The installed version matches the affected version ranges listed in step 1
  4. Determine the installed Solid Edge version number
    Open Solid Edge and navigate to Help > About Solid Edge, or right-click on SolidEdge.exe and select Properties > Details to view the Product Version.
    Affected if The version is Se2022 (any build) or Se2023 (any build, including 223.0)
  5. Check for X_B file parsing usage
    Review whether the software is used to open or process X_B format CAD files. This can be confirmed by searching for recent .x_b files in the system or by checking file association settings for .x_b extension.
    Affected if The software is configured to parse or can be used to open X_B files, and the installed version is within the affected ranges

A user is affected if they have Parasolid (versions 33.1.x before 264, 34.0.x before 252, 34.1.x before 242, or 35.0.x before 170) or Solid Edge Se2022/Se2023 installed AND use X_B file parsing functionality.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 33.1.264 / 34.0.252 / 34.1.242 or later
Fixed in 33.1.26434.0.25234.1.242
Interim mitigation

Update to the patched versions: Parasolid V33.1.264+, V34.0.252+, V34.1.242+, V35.0.170+, Solid Edge V222.0MP12+, or V223.0Update2+. Avoid opening untrusted X_B files from unknown sources as an interim measure.

Recommended fix High confidence

Parasolid V33.1.264 / V34.0.252 / V34.1.242 / V35.0.170; Solid Edge SE2022 V222.0MP12; Solid Edge SE2023 V223.0Update2

  1. 1. Identify the currently installed Parasolid or Solid Edge version from the application's About or Help menu
  2. 2. For Parasolid V33.1.x users: Upgrade to Parasolid V33.1.264 or later
  3. 3. For Parasolid V34.0.x users: Upgrade to Parasolid V34.0.252 or later
  4. 4. For Parasolid V34.1.x users: Upgrade to Parasolid V34.1.242 or later
  5. 5. For Parasolid V35.0.x users: Upgrade to Parasolid V35.0.170 or later
  6. 6. For Solid Edge SE2022 users: Upgrade to V222.0MP12 or later
  7. 7. For Solid Edge SE2023 users: Upgrade to V223.0Update2 or later
  8. 8. After upgrade, validate that X_B file parsing works correctly with legitimate files

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Parasolid Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-46346 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-46346 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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