dbcve.org
3d Visual Enterprise ViewerApplication · Sap

CVE-2022-41189

HIGH · 7.8 CVSS v3.1 Published 2022-10-11
Fix available
A fix is available. Upgrade to 9.0 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
Due to lack of proper memory management, when a victim opens a manipulated AutoCAD (.dwg, TeighaTranslator.exe) file received from untrusted sources in SAP 3D Visual Enterprise Viewer - 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

Memory corruption vulnerability in SAP 3D Visual Enterprise Viewer version 9 when parsing manipulated AutoCAD (.dwg) files. Improper memory management allows either stack-based buffer overflow or dangling pointer reuse (use-after-free), enabling remote code execution when a victim opens a malicious file.

MitigationDo not open AutoCAD (.dwg) files from untrusted sources in SAP 3D Visual Enterprise Viewer. Apply vendor patches when available and consider disabling file preview features or restricting the application to trusted file 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
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. Locate the SAP 3D Visual Enterprise Viewer installation
    Check for the application in the program directory, typically at C:\Program Files\SAP\SAP 3D Visual Enterprise Viewer\ or C:\Program Files (x86)\SAP\SAP 3D Visual Enterprise Viewer\
    Affected if The application directory exists on the system
  2. Identify the installed version
    Right-click on the executable file (typically Viewer.exe or sap3dviewer.exe) within the installation folder, select Properties, and view the File Version in the Details tab
    Affected if The version shown is below 9.0 (for example, 8.0, 7.0, etc.)
  3. Verify the application processes AutoCAD files
    Check whether the user workflow involves opening, previewing, or converting .dwg files using SAP 3D Visual Enterprise Viewer
    Affected if The user regularly opens .dwg files with this application

If the installed version is below 9.0 AND the application is used to open .dwg files, the environment is vulnerable to 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.

dbcve · scoped
Upgrade available Upgrade to 9.0 or later
Fixed in 9.0
Interim mitigation

Do not open AutoCAD (.dwg) files from untrusted sources in SAP 3D Visual Enterprise Viewer. Apply vendor patches when available and consider disabling file preview features or restricting the application to trusted file sources.

Recommended fix High confidence

SAP 3D Visual Enterprise Viewer version 9.0 or latest available version

  1. 1. Identify the current installed version of SAP 3D Visual Enterprise Viewer by opening the application and checking 'Help' > 'About'
  2. 2. Navigate to the SAP Support Portal at https://support.sap.com/ or the official SAP 3D Visual Enterprise Viewer download page
  3. 3. Download SAP 3D Visual Enterprise Viewer version 9.0 or latest available version
  4. 4. Close the application completely before installation
  5. 5. Run the installer with administrative privileges
  6. 6. Follow the on-screen installation prompts to complete the upgrade
  7. 7. After installation, verify the new version by checking 'Help' > 'About' in the application
Caveat Ensure compatibility with existing workflows and any custom integrations; test the new version with your typical AutoCAD (.dwg) files before production deployment

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

Fix this in 3d Visual Enterprise Viewer Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,790
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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