CVE-2022-41166
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 manipulated Wavefront Object (.obj, ObjTranslator.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 · high confidenceA memory management vulnerability in SAP 3D Visual Enterprise Author version 9's ObjTranslator.exe component allows specially crafted Wavefront Object (.obj) files from untrusted sources to cause a denial of service condition, crashing the application until restart.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Verify SAP 3D Visual Enterprise Author installationCheck for the application in the system program files directory, typically under C:\Program Files\SAP or C:\Program Files (x86)\SAP, or look for the application in Add/Remove Programs.Affected if The application is installed and the version is exactly 9.0
-
Locate ObjTranslator.exe componentSearch for ObjTranslator.exe in the SAP 3D Visual Enterprise Author installation directory, commonly found in a bin or subfolder within the main installation path.Affected if ObjTranslator.exe exists in the installation directory, indicating the vulnerable component is present
-
Confirm version numberRight-click on ObjTranslator.exe or the main application executable, select Properties, and check the File Version or Product Version field. Alternatively, use the command: wmic product where "name like 'SAP 3D Visual Enterprise Author'" get versionAffected if The version displays as 9.0 (exact match to the affected version)
-
Check .obj file handling capabilityVerify that .obj file association or import functionality is available in the application. Check File > Open or Import dialogs for Wavefront Object (.obj) file type support.Affected if The application can open or import .obj files, meaning the vulnerable parsing code path is reachable
You are affected if SAP 3D Visual Enterprise Author version 9.0 is installed with the ObjTranslator.exe component and the application supports .obj file processing.
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 dataAvoid opening .obj files from untrusted or unknown sources. Apply vendor patches when available and implement file format validation before processing.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.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,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-41166 — 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-41166 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