dbcve.org
3d Visual Enterprise ViewerApplication · Sap

CVE-2022-41192

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 manipulated Jupiter Tesselation (.jt, JTReader.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 · moderate confidence

Memory management vulnerability in SAP 3D Visual Enterprise Viewer version 9 allows remote denial of service via specially crafted Jupiter Tesselation (.jt) files parsed by the JTReader.x3d component. Opening a malicious JT file from untrusted sources triggers improper memory handling, causing the application to crash and become unavailable until restart.

MitigationDo not open JT files from untrusted or unknown sources in SAP 3D Visual Enterprise Viewer. Apply vendor security patches when released and consider using application sandboxing or alternative file viewers for untrusted JT content.

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. Identify SAP 3D Visual Enterprise Viewer installation
    Check for the presence of the application in the system - typically installed in Program Files or Program Files (x86) with folder name containing 'SAP 3D Visual Enterprise Viewer'
    Affected if The application is installed on the system
  2. Determine installed version number
    Right-click the executable (commonly named 'viewer.exe' or 'SAP 3D Visual Enterprise Viewer.exe'), select Properties, and check the Version tab, or use the application's About/Help menu to view version info
    Affected if The installed version is lower than 9.0 (for example, 8.0, 8.0.1, etc.)
  3. Locate JTReader.x3d component
    Search for the file 'JTReader.x3d' within the application installation directory, typically found in a 'bin' or 'plugins' subfolder
    Affected if The JTReader.x3d component file exists in the application directory, indicating the vulnerable parsing module is present
  4. Verify .jt file handling capability
    Open the application and attempt to open or import a .jt (Jupiter Tessellation) file, or check file association settings for .jt extension
    Affected if The application can open or process .jt files and the JTReader.x3d component is available
  5. Confirm vulnerability trigger condition
    Check whether the application has been used to open .jt files from untrusted or unknown sources
    Affected if The user has opened or intends to open .jt files from untrusted sources in this application

The environment is affected if SAP 3D Visual Enterprise Viewer version 9.0 or higher is NOT installed AND the JTReader.x3d component is present AND the application is used to open .jt 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

Do not open JT files from untrusted or unknown sources in SAP 3D Visual Enterprise Viewer. Apply vendor security patches when released and consider using application sandboxing or alternative file viewers for untrusted JT content.

Recommended fix High confidence

Version 9.0 or later (recommended: latest stable release available on SAP Support Portal)

  1. Navigate to the official SAP Support Portal (launchpad.support.sap.com)
  2. Locate SAP 3D Visual Enterprise Viewer in the software download section
  3. Download version 9.0 or later (ensure it is the latest stable release)
  4. Close any running instances of SAP 3D Visual Enterprise Viewer
  5. Install the downloaded version following SAP's standard installation procedure
  6. Restart the application after installation completes
  7. Verify the installation by checking the application's About/Help section for the version number
Caveat Review SAP's release notes for version 9.x for any feature changes or deprecations before upgrading

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
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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