CVE-2021-27589
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 Scalable Vector Graphics (.SVG) format files received from untrusted sources in SAP 3D Visual Enterprise Viewer version 9, the application crashes 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 confidenceA denial-of-service vulnerability in SAP 3D Visual Enterprise Viewer version 9 allows attackers to crash the application by providing a specially crafted SVG file. When the user opens the malicious SVG file from an untrusted source, the application's SVG parser encounters an error that causes a crash, rendering the application unavailable until restart.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Check if SAP 3D Visual Enterprise Viewer is installedLook in the system for the application: check Add/Remove Programs, or look in Program Files directories (C:\Program Files\SAP or C:\Program Files (x86)\SAP) for a folder named SAP 3D Visual Enterprise ViewerAffected if The application directory exists on the system
-
Identify the installed version numberLocate the main executable (typically named SAP3DVisualEnterpriseViewer.exe), right-click it, select Properties, go to the Details tab, and read the File Version fieldAffected if The version string begins with 9 (such as 9.0.x, 9.0.0.x, or any 9.x release)
-
Confirm SVG file type associationCheck if .svg files are set to open with this viewer - look in Windows Registry under HKCR\.svg\OpenWithProgids or inspect the file type association in the application's options or system default app settingsAffected if SVG files are associated with or can be opened by SAP 3D Visual Enterprise Viewer
-
Determine exposure to untrusted SVG filesCheck user download folders, email attachment handling rules, or network perimeter controls for SVG file processing from external sourcesAffected if Users can receive or download SVG files from untrusted or unknown sources that would be opened in this viewer
Environment is affected if SAP 3D Visual Enterprise Viewer version 9 is installed and users may open SVG files from untrusted sources.
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 dataUntil an official vendor patch is available, instruct users to only open SVG files from trusted sources and consider blocking SVG file types from untrusted email or web sources at the network perimeter.
- Consultation2.0 h
- Testing1.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 $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-27589 — 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-2021-27589 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