dbcve.org
ParasolidApplication · Siemens

CVE-2022-46348

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

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 components used by Solid Edge when parsing specially crafted X_B files. The vulnerability allows writing past the end of an allocated buffer, potentially leading to arbitrary code execution in the context of the current process.

MitigationUpdate affected Parasolid and Solid Edge installations to the patched versions (V33.1.264, V34.0.252, V34.1.242, V35.0.170, V222.0MP12, or V223.0Update2), and avoid opening untrusted X_B files from unknown 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 if Parasolid or Solid Edge is installed
    Check for the presence of Siemens Parasolid components or Solid Edge application on the system. This may be found in program files, or by checking installed programs list.
    Affected if Either Siemens Parasolid or Solid Edge is present on the system
  2. Determine the installed Parasolid version
    Locate the Parasolid version information. This is typically available through the Solid Edge application (About menu), or check version information for Parasolid DLLs if accessible on the system.
    Affected if The exact version cannot be determined or the software is not found
  3. Compare against affected version ranges
    Compare your installed Parasolid version to the following vulnerable ranges: >= 33.1 to < 33.1.264, >= 34.0 to < 34.0.252, >= 34.1 to < 34.1.242, or >= 35.0 to < 35.0.170
    Affected if The installed version falls within any of these ranges (33.1.x, 34.0.x, 34.1.x, or 35.0.x before the patch thresholds)
  4. Determine X_B file processing exposure
    Assess whether the system is configured to parse X_B files, which is the attack vector for this vulnerability. X_B is a Parasolid binary file format.
    Affected if X_B file parsing is enabled or the system processes X_B files from external or untrusted sources

A system is affected if it has Parasolid or Solid Edge installed with a version number matching any of the four vulnerable ranges AND 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 affected Parasolid and Solid Edge installations to the patched versions (V33.1.264, V34.0.252, V34.1.242, V35.0.170, V222.0MP12, or V223.0Update2), and avoid opening untrusted X_B files from unknown sources.

Recommended fix High confidence

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

  1. 1. Identify the current Parasolid or Solid Edge version installed in your environment
  2. 2. For Parasolid V33.1.x users: Upgrade to version V33.1.264 or later
  3. 3. For Parasolid V34.0.x users: Upgrade to version V34.0.252 or later
  4. 4. For Parasolid V34.1.x users: Upgrade to version V34.1.242 or later
  5. 5. For Parasolid V35.0.x users: Upgrade to version V35.0.170 or later
  6. 6. For Solid Edge SE2022 users: Upgrade to version V222.0MP12 or later
  7. 7. For Solid Edge SE2023 users: Upgrade to version V223.0Update2 or later
  8. 8. Obtain the fixed version from Siemens official support portal (cert-portal.siemens.com) or your authorized Siemens distributor
Caveat Standard upgrade risks apply - test in non-production environment before deploying organization-wide

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
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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 locally
dbcve dependency scanner

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