3d Visual Enterprise ViewerApplication · Sap

CVE-2020-6315

MEDIUM · 5.5 CVSS v3.1 Published 2020-10-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
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
SAP 3D Visual Enterprise Viewer, version 9, allows an attacker to send certain manipulated file to the victim, which can lead to leakage of sensitive information when the victim loads the malicious file into the VE viewer, leading to Information Disclosure.

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

SAP 3D Visual Enterprise Viewer version 9 is vulnerable to information disclosure when processing maliciously crafted files. An attacker can send a specially crafted file to a victim; when the victim opens this file in the viewer, it leads to leakage of sensitive information. The CVSS 5.5 score suggests local attack vector or user interaction is required.

MitigationUsers should not open untrusted or unverified files in SAP 3D Visual Enterprise Viewer. Organizations should implement policies restricting file handling and consider applying any available vendor patches for this vulnerability.

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

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
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

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 if SAP 3D Visual Enterprise Viewer is installed
    Check Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall for an entry named 'SAP 3D Visual Enterprise Viewer', or inspect Program Files (x86) for a folder containing 'SAP 3D Visual Enterprise Viewer'.
    Affected if The software is found installed on the system.
  2. Determine the exact installed version
    Locate the main executable (typically named something like 'Viewer.exe' or 'sapseviewer.exe' in the installation directory), right-click and select Properties, then check the Version tab, or run: dir /s "C:\Program Files*\SAP 3D Visual Enterprise Viewer\*.exe" to find the executable and check its version property.
    Affected if The version number shown is exactly 9 (such as 9.0.x.x or 9.0.0.x).
  3. Verify file handling behavior
    Review whether users in the organization routinely open 3D files from untrusted or external sources. Check if there are group policies or endpoint controls restricting file associations for .3d, .3ds, .dae, .obj, .wrl, or other 3D file formats to the SAP viewer.
    Affected if Users have the ability to open untrusted files directly in the viewer without restrictions.
  4. Check for recent file processing activity
    Examine Windows Event Logs under Security or Application logs for recent instances where the SAP viewer executable was used to open files from network shares, email attachments, or download folders.
    Affected if The viewer has recently processed files from untrusted locations.

A system is affected if SAP 3D Visual Enterprise Viewer version 9 is installed and users can open untrusted or maliciously crafted 3D files in the viewer.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Users should not open untrusted or unverified files in SAP 3D Visual Enterprise Viewer. Organizations should implement policies restricting file handling and consider applying any available vendor patches for this vulnerability.

Fix this in 3d Visual Enterprise Viewer Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-6315 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-2020-6315 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