dbcve.org
3d Visual Enterprise AuthorApplication · Sap

CVE-2022-41171

MEDIUM · 5.5 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 →
58/100
Remediation priority · Elevated
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 manipulated CATIA4 Part (.model, CatiaTranslator.exe) file received from untrusted sources in SAP 3D Visual Enterprise Author - version 9, it is possible for the application to crash 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 confidence

A memory management vulnerability in SAP 3D Visual Enterprise Author version 9 allows attackers to cause a denial of service by providing a specially crafted CATIA4 Part (.model) file that triggers improper memory handling, causing the application to crash and require restart.

MitigationAvoid opening CATIA4 Part (.model) files from untrusted sources in SAP 3D Visual Enterprise Author version 9 until an official patch is applied.

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/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 checks

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

  1. Verify SAP 3D Visual Enterprise Author is installed
    Check for the application in the system program directory or look for the executable (typically named sap3dveauthor.exe or similar) in Program Files. Check Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry named SAP 3D Visual Enterprise Author.
    Affected if The application is installed on the system.
  2. Confirm the exact version number is 9.0
    Right-click the executable file and select Properties, then navigate to the Details tab to view the Product Version. Alternatively, run 'reg query "HKLM\SOFTWARE\SAP" /v Version' or check the uninstall registry entry for the version value.
    Affected if The installed version is exactly 9.0.
  3. Check if CATIA4 Part file handling is accessible
    Launch SAP 3D Visual Enterprise Author and attempt to open a .model file via File > Open, or check the supported file formats in the application's options or help documentation. The vulnerability triggers when loading CATIA4 Part (.model) files.
    Affected if The application can open or is configured to handle .model files.
  4. Attempt to open a CATIA4 Part (.model) file to observe behavior
    If a .model file is available, attempt to open it in the application and observe if the program crashes or becomes unresponsive. If no test file is available, this check confirms exposure only if untrusted .model files could be opened.
    Affected if Opening a .model file causes the application to crash or terminate unexpectedly.

The system is affected if SAP 3D Visual Enterprise Author version 9.0 is installed and CATIA4 Part (.model) files can be opened, causing application crashes.

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

Avoid opening CATIA4 Part (.model) files from untrusted sources in SAP 3D Visual Enterprise Author version 9 until an official patch is applied.

Recommended fix Moderate confidence

Check SAP Security Note 3279906 for the specific fixed version or patch; newer versions beyond 9.0 may contain the fix

  1. Check SAP Support Portal (launchpad.support.sap.com) for Security Note #3279906 which addresses this vulnerability
  2. Apply the latest support package or patch for SAP 3D Visual Enterprise Author version 9
  3. If no patch is available, consider upgrading to a newer version of SAP 3D Visual Enterprise Author if released
  4. Alternatively, avoid opening CATIA4 Part (.model) files from untrusted sources until the patch is applied
Caveat Review SAP release notes for any breaking changes when upgrading beyond version 9

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
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-41171 — 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-41171 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