CVE-2022-35171
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 · uneditedWhen a user opens manipulated JPEG 2000 (.jp2, jp2k.x3d) files received from untrusted sources in SAP 3D Visual Enterprise Viewer, the application crashes and becomes temporarily unavailable to the user until restart of the application. The file format details along with their CVE relevant information can be found below
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 confidenceSAP 3D Visual Enterprise Viewer contains a parsing vulnerability when processing specially crafted JPEG 2000 image files (.jp2, jp2k.x3d). When a user opens a malicious file from an untrusted source, the application crashes and becomes unavailable until restarted, resulting in a denial-of-service condition.
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= 9CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify SAP 3D Visual Enterprise Viewer is installedCheck the application list or program files directory for 'SAP 3D Visual Enterprise Viewer' installation. On Windows, check Programs and Features or the installation directory (commonly C:\Program Files\SAP\SAP 3D Visual Enterprise Viewer).Affected if The application is present on the system
-
Confirm the installed version is 9Right-click the executable (typically viewer.exe) and select Properties, then check the File Version in the Details tab. Alternatively, run the viewer and check Help > About.Affected if The installed version is exactly 9.0.x or simply version 9
-
Identify if JPEG 2000 file processing is availableAttempt to open a .jp2 or jp2k.x3d file with the viewer, or check the supported file formats in the application's documentation or file open dialog filters.Affected if The application can open and parse JPEG 2000 format files
-
Check for recent crash or DoS indicatorsReview Windows Event Viewer Application logs for crashes related to sap3dvisualenterpriseviewer.exe, or check for .dmp crash dump files in the application directory.Affected if Recent crashes occurred when opening JPEG 2000 files from untrusted sources
A user is affected if SAP 3D Visual Enterprise Viewer version 9 is installed and the application processes JPEG 2000 (.jp2, jp2k.x3d) files from untrusted sources, potentially causing application crashes.
Generated from the published advisory. Verify against your own configuration.
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 dataAvoid opening JPEG 2000 files from untrusted or unknown sources. Apply vendor patches from SAP when available. Consider using application sandboxing or restricting file handling to trusted sources as a compensating control.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-35171 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-35171 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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