dbcve.org
3d Visual Enterprise ViewerApplication · Sap

CVE-2022-41195

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 EAAmiga Interchange File Format (.iff, 2d.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 · high confidence

A memory corruption vulnerability in SAP 3D Visual Enterprise Viewer version 9 allows remote code execution when processing specially crafted EAAmiga Interchange File Format (.iff, .x3d) files from untrusted sources. The lack of proper memory management enables either a stack-based buffer overflow or use-after-free condition via dangling pointers to overwritten memory.

MitigationDo not open .iff or .x3d files from untrusted or unknown sources in SAP 3D Visual Enterprise Viewer. Apply vendor patches or upgrade to a fixed version when available.

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. Check if SAP 3D Visual Enterprise Viewer is installed
    Search for the application in Windows Add/Remove Programs or Settings > Apps & features. Look for entries named 'SAP 3D Visual Enterprise Viewer'. Also check common installation directories like C:\Program Files\SAP\ or C:\Program Files (x86)\SAP\
    Affected if The application is present on the system
  2. Determine the installed version
    Locate the main executable (typically named SAP3DVisualEnterpriseViewer.exe), right-click it, select Properties, and check the Version tab for the File Version. Alternatively, launch the application and navigate to Help > About
    Affected if The reported version is less than 9.0 (for example, 8.0, 8.x, or any version before 9.0)
  3. Verify the application handles affected file types
    Confirm the viewer can open .iff or .x3d file formats. Check file type associations in Windows by right-clicking a sample .iff or .x3d file, selecting Open with, and verifying SAP 3D Visual Enterprise Viewer is listed. Alternatively, attempt to open such a file with the viewer
    Affected if The viewer is associated with or can open .iff or .x3d files

You are affected if SAP 3D Visual Enterprise Viewer is installed with a version lower than 9.0 and the application is configured to process .iff or .x3d 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
Upgrade available Upgrade to 9.0 or later
Fixed in 9.0
Interim mitigation

Do not open .iff or .x3d files from untrusted or unknown sources in SAP 3D Visual Enterprise Viewer. Apply vendor patches or upgrade to a fixed version when available.

Recommended fix High confidence

SAP 3D Visual Enterprise Viewer version 9.0 or later

  1. 1. Close SAP 3D Visual Enterprise Viewer if it is currently running
  2. 2. Navigate to the official SAP Support Portal at https://launchpad.support.sap.com/
  3. 3. Search for SAP 3D Visual Enterprise Viewer version 9.0 or latest available version
  4. 4. Download the version 9.0 (or later) installer for your platform
  5. 5. Run the installer and follow the on-screen prompts to complete the upgrade
  6. 6. After installation, verify the version by opening the application and checking 'Help' > 'About'
  7. 7. Ensure the installed version is 9.0 or higher
  8. 8. Do not open .iff or 2d.x3d files from untrusted sources even after patching
Caveat Review SAP release notes for version 9.0 to check for any feature changes or compatibility considerations with existing workflows

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
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
40.0 hours of engineering $6,920
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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