CVE-2021-33680
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 · uneditedSAP 3D Visual Enterprise Viewer, version - 9, allows a user to open manipulated CGM file received from untrusted sources which causes buffer overflow and causes the application to crash and becoming temporarily unavailable until the user restarts 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 · high confidenceA buffer overflow vulnerability exists in SAP 3D Visual Enterprise Viewer version 9 when parsing CGM (Computer Graphics Metafile) files. Opening a manipulated CGM file from an untrusted source causes a buffer overflow, resulting in application crash and temporary unavailability until the user restarts the application.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/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 system for installation of SAP 3D Visual Enterprise Viewer. On Windows, look in Program Files for the SAP folder, or check Add/Remove Programs for an entry named 'SAP 3D Visual Enterprise Viewer'.Affected if The application is not installed on the system.
-
Determine the installed versionLocate the main executable (typically named sap3dveviewer.exe or similar in the installation directory) and check its file version property. Alternatively, launch the application and look for version information in the Help or About menu.Affected if The installed version is exactly version 9.
-
Confirm CGM file parsing capability is presentCheck if the application has the ability to open or import CGM files. This may be evident from the application's file open dialog filter, or from associated file associations (.cgm extension handler).Affected if CGM file support is available and the application can open .cgm files.
-
Review recent file access activityCheck application logs, recent documents, or the application's recent files list for any opened .cgm files. On Windows, also check the Windows Jump List or recent files history for the application.Affected if CGM files have been opened with this application.
A user is affected if SAP 3D Visual Enterprise Viewer version 9 is installed and CGM file parsing functionality is present, as the vulnerability triggers when opening a specially crafted CGM file.
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 dataApply the SAP security patch for CVE-2021-33680 when released. Until then, avoid opening CGM files from untrusted sources and implement application isolation to limit the impact of potential crashes.
- Consultation2.0 h
- Implementation1.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-33680 — 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-33680 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