dbcve.org
Solid EdgeWeb browser · Siemens

CVE-2022-47967

HIGH · 7.8 CVSS v3.1 Published 2023-01-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 Solid Edge (All versions < V2023 MP1). The DOCMGMT.DLL contains a memory corruption vulnerability that could be triggered while parsing files in different file formats such as PAR, ASM, DFT. 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 · moderate confidence

Memory corruption vulnerability in Solid Edge's DOCMGMT.DLL library allows attackers to execute arbitrary code by parsing specially crafted PAR, ASM, or DFT files. The vulnerability exists in the file parsing logic and affects all versions prior to V2023 MP1.

MitigationUpgrade to Solid Edge V2023 MP1 or later to obtain the vendor patch. Consider restricting or validating untrusted file imports until the update is applied.

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
Solid EdgeWeb browser
Affected:< se2023= se2023

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. Confirm Solid Edge installation
    Check for the presence of the Solid Edge installation directory, typically found at C:\Program Files\Siemens\Solid Edge<version> or C:\Program Files (x86)\Siemens\Solid Edge<version>. Use File Explorer or PowerShell: Get-ChildItem 'C:\Program Files*\Siemens\' -ErrorAction SilentlyContinue | Where-Object { $_.Name -like 'Solid*' }
    Affected if Solid Edge is not installed on the system
  2. Identify installed Solid Edge version
    Locate the main Solid Edge executable (usually solid edge.exe or se.exe) in the installation folder and check its file version. In Windows, right-click the executable, select Properties, and view the Details tab. Alternatively, use PowerShell: Get-Item 'C:\Program Files\Siemens\Solid Edge*\Program\solid edge.exe' | Select-Object Name, VersionInfo
    Affected if The version cannot be determined or is earlier than V2023 MP1
  3. Verify DOCMGMT.DLL presence
    Confirm that the vulnerable DOCMGMT.DLL library exists in the Solid Edge installation directory. Search for the file: Get-ChildItem 'C:\Program Files*\Siemens\Solid Edge*\' -Recurse -Filter 'DOCMGMT.DLL' -ErrorAction SilentlyContinue
    Affected if DOCMGMT.DLL is not found in the expected Solid Edge directory
  4. Compare version to affected range
    Review the identified Solid Edge version against the affected versions: versions prior to V2023 MP1 (including se2023). The vulnerability affects all versions < se2023 or = se2023. If the installed version is se2022, se2021, or older, the environment is vulnerable. If the version is se2023 (without MP1), it is also vulnerable.
    Affected if Installed version is se2023 (without MP1) or any earlier version such as se2022, se2021, se2020, or prior

A system is affected if Solid Edge is installed with a version prior to V2023 MP1 (including se2023), and the DOCMGMT.DLL library exists for parsing PAR, ASM, or DFT 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Solid Edge V2023 MP1 or later to obtain the vendor patch. Consider restricting or validating untrusted file imports until the update is applied.

Recommended fix High confidence

Solid Edge V2023 MP1

  1. Upgrade Solid Edge to version V2023 MP1 or later to remediate the memory corruption vulnerability in DOCMGMT.DLL

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

Fix this in Solid Edge Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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