dbcve.org
3d Visual Enterprise AuthorApplication · Sap

CVE-2022-39803

HIGH · 7.8 CVSS v3.1 Published 2022-10-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
Due to lack of proper memory management, when a victim opens a manipulated ACIS Part and Assembly (.sat, 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 confidence

This vulnerability in SAP 3D Visual Enterprise Author version 9 stems from improper memory management in the CoreCadTranslator.exe component when parsing ACIS Part and Assembly (.sat) files. Opening a maliciously crafted .sat file from an untrusted source can trigger either a stack-based buffer overflow or use of a dangling pointer referring to overwritten memory space, leading to arbitrary code execution.

MitigationDo not open .sat files from untrusted or unknown sources. Apply available vendor patches from SAP. Consider disabling file associations for .sat files or running the application in a sandboxed environment until a patch is available.

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
3d Visual Enterprise AuthorApplication
Affected:= 9.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm SAP 3D Visual Enterprise Author is installed
    Locate the application in the system - typically found under the SAP installation directory in Program Files, or check Add/Remove Programs for 'SAP 3D Visual Enterprise Author'. Look for CoreCadTranslator.exe in the application bin folder.
    Affected if The application is installed and version 9.0 is confirmed
  2. Verify the exact installed version
    Right-click on CoreCadTranslator.exe, select Properties, and check the File Version under the Details tab. Alternatively, check the program's About or Help > About dialog within the application.
    Affected if Version is reported as exactly 9.0 (the only affected version per vendor advisory)
  3. Check if .sat file association exists
    Search the Windows registry under HKCR\.sat or check file associations in Control Files > Default Programs > Associate a file type. .sat files should appear linked to the SAP application.
    Affected if The .sat file extension is associated with SAP 3D Visual Enterprise Author, meaning the vulnerable parsing component will process these files automatically or on user open action
  4. Inspect CoreCadTranslator.exe presence
    Use Windows Search or file explorer to locate CoreCadTranslator.exe within the SAP installation directory structure, typically in a bin or executable subfolder.
    Affected if The executable exists and the application is used to open .sat files

A user is affected if SAP 3D Visual Enterprise Author version 9.0 is installed with .sat file handling enabled and the CoreCadTranslator.exe component is present to process ACIS Part and Assembly files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Do not open .sat files from untrusted or unknown sources. Apply available vendor patches from SAP. Consider disabling file associations for .sat files or running the application in a sandboxed environment until a patch is available.

Recommended fix Moderate confidence

Obtain the fixed version from SAP Security Note 3268702 - consult SAP Support for the specific version number

  1. Contact SAP Support or visit the SAP Security Notes page (https://launchpad.support.sap.com/) to obtain the specific security patch for CVE-2022-39803
  2. Verify the current installed version of SAP 3D Visual Enterprise Author
  3. Apply the patch or upgrade to the fixed version as specified in the SAP Security Note
  4. Restart the application after applying the patch
  5. Validate the fix by testing with the manipulated .sat file in a controlled environment to confirm the vulnerability is remediated
Caveat Review SAP Security Note 3268702 for any compatibility considerations before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in 3d Visual Enterprise Author Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-39803 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-39803 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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