CVE-2022-41172
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 AutoCAD (.dxf, TeighaTranslator.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 allows RCE via manipulated AutoCAD (.dxf) files. Insufficient memory management during file parsing enables stack-based buffer overflows or dangling pointer reuse, where overwritten memory space is accessed, leading to arbitrary 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.
-
Check if SAP 3D Visual Enterprise Author is installedLook for the application in the Windows Programs and Features list, or check the installation directory under Program Files for a folder named 'SAP 3D Visual Enterprise Author' or similarAffected if The software is installed on the system
-
Identify the installed versionOpen the application and check Help > About, or locate the executable (typically named '3DVisualEnterpriseAuthor.exe' or similar) and view its file properties for version informationAffected if The version is exactly 9.0 (the equals sign indicates only version 9.0 is affected, not a range)
-
Confirm .dxf file handling capability existsCheck if the application has import or file type support for .dxf files - this can be verified by opening the application and checking File > Open or File > Import supported formats, or by searching for .dxf related DLLs or filters in the installation directoryAffected if .dxf file import or processing capability is present in the installation
-
Inspect for recently opened or suspicious .dxf filesCheck the application's recent files list, temp directories, or user download folders for .dxf files that may have been opened from untrusted sourcesAffected if There are .dxf files from untrusted or unknown sources that have been opened with this application
A system is affected if SAP 3D Visual Enterprise Author version 9.0 is installed and .dxf files can be processed by the application - the vulnerability requires the user to open a malicious .dxf file.
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 dataDo not open AutoCAD (.dxf) files from untrusted sources in SAP 3D Visual Enterprise Author. Apply vendor patches when available and implement endpoint detection for suspicious file operations.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-41172 — 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-41172 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