dbcve.org
3d Visual Enterprise AuthorApplication · Sap

CVE-2022-39806

HIGH · 7.8 CVSS v3.1 Published 2022-10-11
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
Due to lack of proper memory management, when a victim opens a manipulated SolidWorks Drawing (.slddrw, CoreCadTranslator.exe) file received from untrusted sources in SAP 3D Visual Enterprise Author - version 9, it is possible that a Remote Code Execution can be triggered when payload forces a stack-based overflow or a re-use of dangling pointer which refers to overwritten space in memory.

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

This vulnerability exists in CoreCadTranslator.exe within SAP 3D Visual Enterprise Author version 9. When parsing a maliciously crafted SolidWorks Drawing file (.slddrw) from untrusted sources, improper memory management allows either a stack-based buffer overflow or a dangling pointer reuse condition where the pointer references overwritten memory space, leading to remote code execution.

MitigationDo not open .slddrw files from untrusted or unknown sources. Apply vendor patches when released. Consider file parsing sandboxing and input validation as defense-in-depth measures.

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
3d Visual Enterprise AuthorApplication
Affected:= 9.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. Verify SAP 3D Visual Enterprise Author is installed
    Check program files for 'SAP 3D Visual Enterprise Author' directory, or query registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for display name containing 'SAP 3D Visual Enterprise Author'. Check version in the application directory or via the application's executable properties.
    Affected if The application is installed and version is 9.0 exactly.
  2. Locate the vulnerable CoreCadTranslator.exe component
    Search for CoreCadTranslator.exe in the SAP 3D Visual Enterprise Author installation directory (typically C:\Program Files\SAP\SAP 3D Visual Enterprise Author\ or C:\Program Files (x86)\SAP\SAP 3D Visual Enterprise Author\).
    Affected if CoreCadTranslator.exe exists in the version 9.0 installation path.
  3. Confirm .slddrw file parsing functionality is present
    Check if the application has file association handlers for .slddrw extension, or review application logs/settings for import/conversion capabilities that include SolidWorks Drawing support.
    Affected if The application is configured to handle or import .slddrw (SolidWorks Drawing) files.
  4. Inspect recent file processing activity
    Review application logs, Windows prefetch, or file system activity logs for any recent .slddrw file imports or conversions performed by the CoreCadTranslator.exe component.
    Affected if The system has processed .slddrw files, particularly from untrusted or unknown sources.

A user is affected if SAP 3D Visual Enterprise Author version 9.0 is installed with CoreCadTranslator.exe present and the system processes .slddrw files, especially from untrusted sources.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Do not open .slddrw files from untrusted or unknown sources. Apply vendor patches when released. Consider file parsing sandboxing and input validation as defense-in-depth measures.

Fix this in 3d Visual Enterprise Author Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,700
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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