CVE-2022-41205
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 · uneditedSAP GUI allows an authenticated attacker to execute scripts in the local network. On successful exploitation, the attacker can gain access to registries which can cause a limited impact on confidentiality and high impact on availability 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 confidenceSAP GUI for Windows contains a vulnerability that allows an authenticated attacker to execute scripts within the local network. Successful exploitation grants the attacker access to Windows registries, resulting in limited confidentiality impact but high availability impact on the affected application.
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= 7.70CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/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.
-
Confirm SAP GUI for Windows is installedCheck for SAP GUI installation by looking for the program in Windows Control Panel > Programs and Features, or check for the presence of SAP GUI-related directories such as C:\Program Files\SAP\FrontEnd\SAPGUI or C:\Program Files (x86)\SAP\FrontEnd\SAPGUIAffected if SAP GUI for Windows is not installed on the system
-
Identify the installed SAP GUI versionOpen SAP Logon (the SAP GUI application), click Help > About SAP Logon, or check the version in Windows Control Panel > Programs and Features under SAP GUI for Windows propertiesAffected if The displayed version is 7.70
-
Verify exact version numberCross-reference the version found in Help > About or Programs and Features - confirm it shows exactly 7.70 with no additional patch level indicatorsAffected if The version is reported as precisely 7.70 (any minor version differences indicate a different patch level)
-
Assess network exposureReview network configuration to determine if the system running SAP GUI is accessible from untrusted network segments, and check if the SAP GUI is configured to connect to external or less-trusted SAP systemsAffected if The SAP GUI client can connect to systems outside a trusted network environment
The environment is affected only if SAP GUI for Windows is installed and the exact installed version is 7.70, combined with network exposure to untrusted systems where an authenticated attacker could exploit script execution capabilities.
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 dataApply the relevant SAP security patch for this vulnerability. Additionally, restrict network access to trusted systems and limit SAP GUI user privileges to reduce the attack surface.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-41205 — 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-41205 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