CVE-2022-39804
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 SolidWorks Part (.sldprt, CoreCadTranslator.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 · high confidenceMemory corruption vulnerability in SAP 3D Visual Enterprise Author version 9 (CoreCadTranslator.exe) allows RCE via malformed SolidWorks Part (.sldprt) files. The lack of proper memory management enables stack-based buffer overflow or dangling pointer reuse when parsing untrusted files.
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 version 9 is installedCheck installed programs list in Windows Control Panel > Programs and Features, or run: Get-ItemProperty 'HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like '*SAP 3D Visual Enterprise Author*'} | Select-Object DisplayName, DisplayVersionAffected if DisplayVersion shows 9.0 exactly (9.0.0.x variants may also be affected)
-
Confirm CoreCadTranslator.exe component is presentSearch for CoreCadTranslator.exe in the installation directory. Default path: C:\Program Files\SAP\SAP 3D Visual Enterprise Author 9\ or search entire system: Get-ChildItem -Path C:\ -Filter CoreCadTranslator.exe -Recurse -ErrorAction SilentlyContinueAffected if CoreCadTranslator.exe exists on the system (this is the vulnerable component)
-
Check if .sldprt file association exists for the softwareCheck Windows file type associations for .sldprt extension: Get-ItemProperty 'HKCR:\.sldprt' or check Default Programs association for SolidWorks Part filesAffected if SAP 3D Visual Enterprise Author is registered as handler for .sldprt files, enabling automatic parsing
-
Inspect recent .sldprt file access or processingReview Windows Event Viewer for recent file access events on .sldprt files, or check browser/download history and recent documents folder for .sldprt files opened with SAP 3D Visual Enterprise AuthorAffected if User has recently opened .sldprt files with this software, indicating potential exposure
User is affected if SAP 3D Visual Enterprise Author version 9.0 is installed with CoreCadTranslator.exe and the software handles .sldprt files, exposing the system to the vulnerability when processing untrusted 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.
dbcve · scopedApply vendor patch from SAP for version 9; until patch available, implement compensating controls such as disabling file preview, blocking .sldprt attachments at email gateway, and user awareness training to avoid opening files from untrusted sources.
SAP 3D Visual Enterprise Author (fixed version per SAP security note)
- Check SAP Support Portal (launchpad.support.sap.com) for the latest patch or security note related to CVE-2022-39804
- Identify the fixed version of SAP 3D Visual Enterprise Author that addresses this vulnerability
- Download and install the updated version from SAP's official software distribution center
- Verify the installation by checking the product version under Help > About
- Implement standard security controls: scan downloaded files with antivirus before opening, and exercise caution with files from untrusted sources
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2022-39804 — 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-39804 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