3d Visual Enterprise ViewerApplication · Sap

CVE-2022-32235

MEDIUM · 5.5 CVSS v3.1 Published 2022-06-14
Fix available
A fix is available. Upgrade to after 9.0 or later.
See remediation →
58/100
Remediation priority · Elevated
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
When a user opens manipulated AutoCAD (.dwg, TeighaTranslator.exe) files received from untrusted sources in SAP 3D Visual Enterprise Viewer, the application crashes and becomes temporarily unavailable to the user until restart of the application.

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

This is a denial-of-service vulnerability in SAP 3D Visual Enterprise Viewer where opening specially crafted AutoCAD (.dwg) files from untrusted sources causes the TeighaTranslator.exe component to crash, rendering the application unavailable until restart.

MitigationUsers should refrain from opening AutoCAD files from untrusted or unknown sources. Consider implementing file origin warnings or restricting file type handling from external 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
3d Visual Enterprise ViewerApplication
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
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/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. Check if SAP 3D Visual Enterprise Viewer is installed
    Look for the application in Add/Remove Programs (Windows) or check for the installation directory under Program Files, typically named 'SAP 3D Visual Enterprise Viewer'. Also check the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries containing 'SAP' and '3D Visual Enterprise Viewer'.
    Affected if The application is found installed on the system
  2. Identify the installed version
    Right-click the main application executable (usually named something like 'SAP3DVisualEnterpriseViewer.exe' in the installation folder) and select Properties, then check the Details tab for the File Version. Alternatively, check the registry uninstall entry for the DisplayVersion value.
    Affected if The version number is 9.0 or lower (any version <= 9.0)
  3. Verify TeighaTranslator.exe component exists
    Navigate to the SAP 3D Visual Enterprise Viewer installation directory (typically in Program Files or Program Files (x86)) and check for the presence of TeighaTranslator.exe. This is the component that processes .dwg files and crashes.
    Affected if TeighaTranslator.exe is present in the application directory
  4. Confirm .dwg file handling capability
    Check if the application has file association handlers configured for .dwg files. This can be verified by searching the Windows registry under HKCR\.dwg or by attempting to open a .dwg file with the viewer to see if it attempts processing.
    Affected if The application is configured to open or process .dwg AutoCAD files

If SAP 3D Visual Enterprise Viewer version 9.0 or lower is installed with the TeighaTranslator.exe component and is configured to handle .dwg files, the environment is affected by this CVE.

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
Upgrade available Upgrade to a release after 9.0
Interim mitigation

Users should refrain from opening AutoCAD files from untrusted or unknown sources. Consider implementing file origin warnings or restricting file type handling from external sources.

Fix this in 3d Visual Enterprise Viewer Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-32235 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-32235 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