CVE-2022-41174
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 Right Hemisphere Material (.rhm, rh.x3d) 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 confidenceA memory management vulnerability in SAP 3D Visual Enterprise Author version 9 allows a denial of service when a user opens a specially crafted Right Hemisphere Material file (.rhm or rh.x3d) from an untrusted source, causing the application to crash and require 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 is installedCheck the installed programs list in Windows Control Panel > Programs and Features, or use the command: reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall" /s | findstr "3D Visual Enterprise Author"Affected if The application appears in the installed programs list
-
Confirm the installed version is exactly 9.0Right-click the application in Programs and Features to view version details, or check the executable properties at the installation path (typically C:\Program Files\SAP\SAP 3D Visual Enterprise Author\veauthor.exe) by right-clicking the .exe and selecting Properties > DetailsAffected if The version listed is exactly 9.0 (any subversion like 9.0.x would also be affected since the affected range is version 9.0)
-
Determine if the application can process .rhm or rh.x3d file typesCheck file association settings: Open Default Programs > Set Associations in Windows, or examine the registry keys under HKCR\.rhm and HKCR\.x3d (or rh.x3d) to see if they are mapped to the SAP applicationAffected if The .rhm or rh.x3d file extensions are associated with SAP 3D Visual Enterprise Author, making the application vulnerable when opening untrusted files
A user is affected if SAP 3D Visual Enterprise Author version 9.0 is installed and the application is configured to open .rhm or rh.x3d files, allowing specially crafted files to trigger the memory management flaw and cause a crash.
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 dataOrganizations should implement controls to prevent users from opening file attachments from untrusted sources, particularly .rhm and rh.x3d files; consider email/endpoint detection to block these file types until SAP releases an official patch.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-41174 — 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-41174 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