dbcve.org
3d Visual Enterprise ViewerApplication · Sap

CVE-2022-41197

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 VRML Worlds (.wrl, vrml.x3d) file received from untrusted sources in SAP 3D Visual Enterprise Viewer - version 9, it is possible for the application to crash 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 · high confidence

A memory management vulnerability in SAP 3D Visual Enterprise Viewer version 9 allows attackers to cause a denial of service by supplying a specially crafted VRML Worlds file (.wrl or vrml.x3d). The lack of proper memory handling during VRML file parsing leads to application crash, requiring user restart to regain functionality.

MitigationOrganizations should instruct users to avoid opening VRML files from untrusted sources and apply vendor patches when released by SAP. Consider implementing file type restrictions or email gateway filters to block unsolicited .wrl/.x3d attachments.

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. Verify SAP 3D Visual Enterprise Viewer is installed
    Check for the application in Program Files (typically C:\Program Files\SAP\SAP 3D Visual Enterprise Viewer) or look for the executable (Viewer.exe) on the system
    Affected if The application is present on the system
  2. Determine installed version number
    Right-click Viewer.exe, select Properties, then view the Details tab for the Product Version field. Alternatively, open the application and go to Help > About
    Affected if Version number is less than 9.0 (for example, 8.0, 8.0.1, etc.)
  3. Check for VRML file type associations
    Look for .wrl or .x3d file associations registered with the Viewer, or check if the application has VRML import capability enabled in its settings
    Affected if VRML file types are associated with the Viewer and the version is below 9.0
  4. Review application crash logs
    Check Windows Event Viewer under Application logs for recent crashes of sap3dvisualenterpriseviewer.exe, particularly those occurring when opening .wrl or .x3d files
    Affected if Crashes are logged when opening VRML files and version is below 9.0

A user is affected if SAP 3D Visual Enterprise Viewer version below 9.0 is installed and users open VRML (.wrl or .x3d) files, which can trigger the memory handling flaw and cause application crashes.

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

Organizations should instruct users to avoid opening VRML files from untrusted sources and apply vendor patches when released by SAP. Consider implementing file type restrictions or email gateway filters to block unsolicited .wrl/.x3d attachments.

Recommended fix Moderate confidence

SAP 3D Visual Enterprise Viewer version 9.0

  1. Identify the current version of SAP 3D Visual Enterprise Viewer installed on the system
  2. Navigate to the official SAP support portal at https://launchpad.support.sap.com/ or www.sap.com
  3. Locate and download SAP 3D Visual Enterprise Viewer version 9.0 or later
  4. Close any running instances of SAP 3D Visual Enterprise Viewer
  5. Run the installer for version 9.0 or later to upgrade the application
  6. Restart the system if prompted by the installer
  7. Verify the installed version is 9.0 or higher after installation completes
  8. Avoid opening VRML Worlds files (.wrl, vrml.x3d) from untrusted sources until the upgrade is applied

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

Fix this in 3d Visual Enterprise Viewer Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,540
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,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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