CVE-2022-39805
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 · uneditedDue to lack of proper memory management, when a victim opens a manipulated Computer Graphics Metafile (.cgm, CgmTranslator.exe) file received from untrusted sources in SAP 3D Visual Enterprise Author - version 9, it is possible that a Remote Code Execution can be triggered when payload forces a stack-based overflow or a re-use of dangling pointer which refers to overwritten space in memory.
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 Author version 9's CgmTranslator.exe has improper memory management when parsing Computer Graphics Metafile (.cgm) files. When a user opens a malicious .cgm file from an untrusted source, the vulnerability can trigger either a stack-based buffer overflow or reuse of a dangling pointer pointing to overwritten memory, leading to remote code execution.
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= 9.0CVSS 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.
-
Verify SAP 3D Visual Enterprise Author installationLocate the installation directory of SAP 3D Visual Enterprise Author on the system. Common paths include C:\Program Files\SAP or C:\Program Files (x86)\SAP. Check for the presence of the main application folder.Affected if The application is not installed on the system.
-
Confirm installed version is 9.0Right-click on the main executable (typically VisualEnterpriseAuthor.exe or similar) and select Properties, then view the Details tab to see the File Version. Alternatively, open the application and check Help > About.Affected if The installed version is 9.0.
-
Locate vulnerable component CgmTranslator.exeSearch the installation directory for CgmTranslator.exe file. This component handles Computer Graphics Metafile (.cgm) file processing.Affected if CgmTranslator.exe exists in the installation directory.
-
Check for .cgm file processing capabilityVerify that the application or its components can process .cgm files. This may be confirmed by checking file associations, registry entries for .cgm handling, or attempting to open a .cgm file.Affected if The application can parse .cgm files and CgmTranslator.exe is accessible.
A user is affected if SAP 3D Visual Enterprise Author version 9.0 is installed with CgmTranslator.exe present and capable of processing .cgm files.
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 vendor patch from SAP or implement compensating controls such as blocking .cgm file attachments at email gateways, disabling CgmTranslator.exe, or restricting execution via application control policies until the patch is available.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-39805 — 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-39805 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