dbcve.org
3d Visual Enterprise ViewerApplication · Sap

CVE-2022-41193

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 Encapsulated Post Script (.eps, ai.x3d) 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 · moderate confidence

Memory corruption vulnerability in SAP 3D Visual Enterprise Viewer version 9 where malformed .eps or ai.x3d files from untrusted sources cause stack-based buffer overflows or dangling pointer reuse, allowing arbitrary code execution.

MitigationAvoid opening .eps or ai.x3d files from untrusted sources; apply SAP vendor patches when released and implement endpoint detection for suspicious file handling.

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. Confirm SAP 3D Visual Enterprise Viewer installation
    Check for the application in installed programs (Windows: Control Panel > Programs and Features, or check C:\Program Files\SAP for the executable)
    Affected if The application is installed on the system
  2. Identify installed version number
    Right-click the executable (typically viewer.exe or similar in the SAP 3D Visual Enterprise Viewer installation folder), select Properties, and check the File Version on the Details tab, or run: Get-Item 'C:\Program Files\SAP\3D Visual Enterprise Viewer\viewer.exe' | Select-Object VersionInfo
    Affected if The version is lower than 9.0 (e.g., 8.0, 7.x, etc.)
  3. Verify .eps and ai.x3d file handling capability
    Check if the viewer has file association handlers registered for .eps or ai.x3d extensions, or attempt to open a sample .eps or ai.x3d file to confirm the viewer processes these types
    Affected if The viewer can open or is associated with .eps or ai.x3d file types
  4. Inspect for recent .eps or ai.x3d file activity
    Review Windows Event Viewer logs, application logs, or file history for recently opened .eps or ai.x3d files, particularly from downloads, email attachments, or shared network locations
    Affected if Any .eps or ai.x3d files from untrusted or unknown sources have been opened recently

The system is affected if SAP 3D Visual Enterprise Viewer version below 9.0 is installed AND the viewer is used to open .eps or ai.x3d files 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.

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

Avoid opening .eps or ai.x3d files from untrusted sources; apply SAP vendor patches when released and implement endpoint detection for suspicious file handling.

Recommended fix Moderate confidence

SAP 3D Visual Enterprise Viewer version 9.0 or later

  1. Download SAP 3D Visual Enterprise Viewer version 9.0 or later from the official SAP website
  2. Verify the integrity of the downloaded installer using SHA256 checksums provided by SAP
  3. Close any running instances of SAP 3D Visual Enterprise Viewer
  4. Run the installer with appropriate administrator privileges
  5. Follow the on-screen installation wizard prompts to complete the upgrade
  6. After installation, verify the installed version by checking About or Help menu to confirm version 9.0 or later is running
  7. Ensure all users are informed to avoid opening .eps or ai.x3d files from untrusted sources as a supplementary security measure

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

Fix this in 3d Visual Enterprise Viewer Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA5.0 h
33.0 hours of engineering $5,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 $9,216.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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