dbcve.org
3d Visual Enterprise AuthorApplication · Sap

CVE-2022-41180

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 Portable Document Format (.pdf, PDFPublishing.dll) 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

A memory corruption vulnerability in PDFPublishing.dll in SAP 3D Visual Enterprise Author version 9 allows RCE via a malicious PDF file. The root cause is improper memory management that can trigger either a stack-based buffer overflow or dangling pointer reuse when the victim opens a crafted PDF from untrusted sources.

MitigationApply vendor patches when available. Until then, enforce strict controls: scan all PDF files with updated anti-malware, disable PDF rendering capabilities if not required, and never open PDF attachments from untrusted sources.

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. Identify if SAP 3D Visual Enterprise Author is installed
    Check the installed programs on the system for 'SAP 3D Visual Enterprise Author' via Windows Control Panel > Programs and Features, or query the registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries containing 'SAP 3D Visual Enterprise Author'.
    Affected if The application is present on the system
  2. Determine the installed version
    Right-click the application executable (typically in Program Files or Program Files (x86)), select Properties, and check the Version tab, or right-click PDFPublishing.dll in the bin directory and inspect its version properties.
    Affected if The version is exactly 9.0 (the affected version)
  3. Locate the vulnerable PDFPublishing.dll component
    Search for PDFPublishing.dll within the SAP 3D Visual Enterprise Author installation directory (commonly found in C:\Program Files\SAP\SAP 3D Visual Enterprise Author\ or subdirectories).
    Affected if PDFPublishing.dll exists in the installation folder and the application is version 9.0
  4. Verify PDF import capability is enabled
    Check the application's configuration files or settings for PDF import or publishing features that load PDFPublishing.dll. This may be in application preferences, plugin settings, or file association configurations.
    Affected if PDF import or publishing features are accessible or enabled in the application
  5. Confirm exposure to untrusted PDF sources
    Review recent file access logs, document history, or the application's recent files list to identify if any PDF files from untrusted or external sources have been opened.
    Affected if Users have opened PDF files from untrusted or unknown sources using the application

A user is affected if SAP 3D Visual Enterprise Author version 9.0 is installed with PDFPublishing.dll present and PDF functionality is enabled or has been used to open files from untrusted sources.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patches when available. Until then, enforce strict controls: scan all PDF files with updated anti-malware, disable PDF rendering capabilities if not required, and never open PDF attachments from untrusted sources.

Fix this in 3d Visual Enterprise Author Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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