dbcve.org
3d Visual Enterprise ViewerApplication · Sap

CVE-2022-41191

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 Jupiter Tesselation (.jt, JTReader.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 Jupiter Tesselation (.jt) files. The vulnerability stems from improper memory management enabling either stack-based buffer overflow or use-after-free conditions where a dangling pointer references overwritten memory space. User interaction is required (opening a malicious file), and the attack can be triggered via .jt or JTReader.x3d file formats.

MitigationApply vendor-supplied patches from SAP when available; until then, enforce strict policies against opening .jt or x3d files from untrusted sources and consider disabling the viewer or deploying application sandboxing for affected systems.

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 installation
    Check for the application in standard installation directories such as C:\Program Files\SAP\SAP 3D Visual Enterprise Viewer, or query the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries containing 'SAP 3D Visual Enterprise Viewer'
    Affected if The application is found installed on the system
  2. Determine installed version number
    Right-click on the main executable (typically Viewer.exe or Sap3DVisualEnterpriseViewer.exe) in the installation folder, select Properties, and view the File Version details. Alternatively, read the version from the registry uninstall key identified in step 1
    Affected if The version is below 9.0 (for example, 8.0, 8.0.1, etc.)
  3. Confirm file handler registration for vulnerable formats
    Check Windows file association settings for .jt and .x3d extensions by querying HKCR\.jt and HKCR\.x3d registry keys, or by viewing file type associations in Default Programs. Verify if either extension is associated with the SAP 3D Visual Enterprise Viewer executable
    Affected if The .jt or .x3d file extensions are associated with the installed SAP viewer application
  4. Assess user exposure to malicious files
    Review system or browser download locations, email attachments, and network share folders for existing .jt or .x3d files that may have been received from untrusted sources
    Affected if Users have the ability to download or receive .jt or .x3d files and open them with the viewer

The system is affected if SAP 3D Visual Enterprise Viewer version below 9.0 is installed AND the viewer is configured to handle .jt or .x3d file formats, allowing a user to open a specially crafted malicious file.

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

Apply vendor-supplied patches from SAP when available; until then, enforce strict policies against opening .jt or x3d files from untrusted sources and consider disabling the viewer or deploying application sandboxing for affected systems.

Recommended fix High confidence

SAP 3D Visual Enterprise Viewer version 9.0

  1. 1. Obtain the latest version of SAP 3D Visual Enterprise Viewer from the official SAP Support Portal (https://support.sap.com)
  2. 2. Download SAP 3D Visual Enterprise Viewer version 9.0 or later
  3. 3. Close any running instances of SAP 3D Visual Enterprise Viewer
  4. 4. Uninstall the current version of SAP 3D Visual Enterprise Viewer from the system
  5. 5. Install the downloaded version 9.0 or later
  6. 6. Verify the installation by checking the version number in the application's About section
  7. 7. Ensure all users are informed to only open .jt files from trusted sources as an additional precaution

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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
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,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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