dbcve.org
ParasolidApplication · Siemens

CVE-2022-46349

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 read 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-19384)

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

The vulnerability is an out-of-bounds read in Parasolid and Solid Edge applications when parsing specially crafted X_B CAD files. The parser reads past the end of an allocated memory structure, which can be leveraged by attackers to execute arbitrary code in the context of the current process.

MitigationApply the vendor-supplied patches to reach the fixed versions (Parasolid V33.1.264+, V34.0.252+, V34.1.242+, V35.0.170+; Solid Edge V222.0MP12+, 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 Parasolid installation
    Locate the Parasolid installation directory or check product documentation for the installed version. Common locations include the Siemens installation folders or check the application's 'About' information.
    Affected if Parasolid is installed with a version matching the affected ranges: >= 33.1 and < 33.1.264; >= 34.0 and < 34.0.252; >= 34.1 and < 34.1.242; or >= 35.0 and < 35.0.170
  2. Identify Solid Edge installation
    Locate the Solid Edge installation or check the application's version information through Help > About in the Solid Edge interface.
    Affected if Solid Edge is installed and uses an affected Parasolid version underneath, particularly if the Solid Edge version is prior to V222.0MP12 or V223.0Update2
  3. Verify the exact Parasolid version number
    Use the Parasolid version information dialog, check the binary file properties of the core Parasolid library (typically pxkernel.dll or similar), or query through the application's version API if available.
    Affected if The installed version falls within any of the following ranges: 33.1.0 through 33.1.263, 34.0.0 through 34.0.251, 34.1.0 through 34.1.241, or 35.0.0 through 35.0.169
  4. Confirm X_B CAD file handling capability
    Determine if the installed product can import or open X_B format files. Check file import options or try opening a test X_B file if available.
    Affected if The product can parse X_B files and the version is within the affected ranges listed above, making the out-of-bounds read vulnerability reachable

You are affected if Parasolid or a Parasolid-based product (like Solid Edge) is installed with a version matching any of the affected ranges and the application can process X_B CAD 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

Apply the vendor-supplied patches to reach the fixed versions (Parasolid V33.1.264+, V34.0.252+, V34.1.242+, V35.0.170+; Solid Edge V222.0MP12+, 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 major version line in use)

  1. Identify the currently installed Parasolid version (e.g., by checking About or version information in the application)
  2. Determine which major version line you are on (V33.1, V34.0, V34.1, or V35.0)
  3. Obtain the appropriate fixed version from Siemens: for V33.1 upgrade to V33.1.264, for V34.0 upgrade to V34.0.252, for V34.1 upgrade to V34.1.242, for V35.0 upgrade to V35.0.170
  4. Download the fixed Parasolid version from the Siemens customer portal or support channels
  5. Apply the update following standard Siemens update procedures
  6. Verify the update was successful by confirming the installed version matches the target fixed version
  7. Exercise caution when opening untrusted X_B files in the updated software

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

Fix this in Parasolid Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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