dbcve.org
ParasolidApplication · Siemens

CVE-2022-46347

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-19079)

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

An out-of-bounds write vulnerability exists in Parasolid and Solid Edge when parsing specially crafted X_B files. The parsing code writes past the end of an allocated memory buffer, causing memory corruption that can be leveraged for arbitrary code execution in the context of the current process.

MitigationUpdate Parasolid to V33.1.264+, V34.0.252+, V34.1.242+, or V35.0.170+ and Solid Edge to V222.0MP12+ or V223.0Update2+. Until patched, avoid opening X_B files from untrusted sources.

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

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 Parasolid installation
    Locate the Parasolid installation directory or check the Siemens software inventory on the system
    Affected if Parasolid software is found on the system
  2. Determine Parasolid version
    Find the version information for the installed Parasolid component (check version file, about dialog, or product information)
    Affected if Unable to determine version information
  3. Compare version to affected ranges
    Check if the installed Parasolid version falls within any of these vulnerable ranges: >= 33.1 but < 33.1.264, >= 34.0 but < 34.0.252, >= 34.1 but < 34.1.242, or >= 35.0 but < 35.0.170
    Affected if Installed version matches one of these vulnerable ranges
  4. Identify Solid Edge installation
    Locate Solid Edge installation if present (this product also uses the vulnerable Parasolid component)
    Affected if Solid Edge software is found on the system
  5. Check X_B file handling usage
    Determine if the system or application processes X_B files (the vulnerable file format)
    Affected if X_B file parsing is routinely performed on the system

The environment is affected if Parasolid or Solid Edge with a vulnerable Parasolid version (within the ranges listed) is installed AND the system processes X_B files.

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 Parasolid to V33.1.264+, V34.0.252+, V34.1.242+, or V35.0.170+ and Solid Edge to V222.0MP12+ or V223.0Update2+. Until patched, avoid opening X_B files from untrusted sources.

Recommended fix High confidence

Parasolid: V33.1.264, V34.0.252, V34.1.242, or V35.0.170 (depending on current version line); Solid Edge: V222.0MP12 or V223.0Update2

  1. 1. Identify the current Parasolid or Solid Edge version by checking the application's About or Help menu
  2. 2. For Parasolid V33.1.x, upgrade to V33.1.264 or later
  3. 3. For Parasolid V34.0.x, upgrade to V34.0.252 or later
  4. 4. For Parasolid V34.1.x, upgrade to V34.1.242 or later
  5. 5. For Parasolid V35.0.x, upgrade to V35.0.170 or later
  6. 6. For Solid Edge SE2022, upgrade to V222.0MP12 or later
  7. 7. For Solid Edge SE2023, upgrade to V223.0Update2 or later
  8. 8. Verify the update was applied successfully and test that X_B file parsing works correctly
Caveat Upgrade to new Parasolid/Solid Edge versions may introduce file format changes; ensure compatibility with existing workflows and test critical X_B files after patching

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

Fix this in Parasolid Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-46347 — 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-46347 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