CVE-2023-32113
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 for Windows - version 7.70, 8.0, allows an unauthorized attacker to gain NTLM authentication information of a victim by tricking it into clicking a prepared shortcut file. Depending on the authorizations of the victim, the attacker can read and modify potentially sensitive information after successful exploitation.
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 vulnerability in SAP GUI for Windows versions 7.70 and 8.0 allows attackers to steal NTLM authentication credentials by tricking users into clicking malicious shortcut files. When a victim clicks a prepared .lnk file, the application attempts to authenticate to a remote resource controlled by the attacker, exposing NTLM credentials that can be replayed for unauthorized access to SAP systems and data.
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.70= 7.70= 8.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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
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.
-
Identify SAP GUI for Windows versionOpen SAP GUI, go to 'Help' > 'About SAP GUI' or check the executable version by right-clicking the saplogon.exe file and selecting 'Properties' > 'Details'. Compare the displayed version against the affected ranges: versions 7.70, 8.0, or any version below 7.70.Affected if The installed version is 7.70, 8.0, or any version lower than 7.70.
-
Confirm NTLM authentication is in useIn SAP GUI connection properties, examine the authentication method configured for your SAP system connections. Check if 'SAP Secure Network Communication' is disabled or if the system is configured to use NTLM authentication instead of SAP-specific authentication mechanisms.Affected if NTLM authentication is enabled or SAP SNC is not configured, making NTLM credential exposure possible.
-
Verify SMB signing status on WindowsOpen Command Prompt as Administrator and run 'Get-SmbServerConfiguration | Select-Object RequireSecuritySignature' to check if SMB signing is enforced on the local system.Affected if SMB signing is not enabled, meaning captured NTLM credentials could be replayed without resistance.
-
Inspect shortcut file handling behaviorReview whether users in your environment have permissions to create or modify .lnk files in locations accessible by SAP GUI processes, or if there are group policy restrictions preventing execution of untrusted shortcut files.Affected if Users can create or execute malicious .lnk files without restriction, enabling the credential theft vector.
You are affected if SAP GUI for Windows version 7.70 or 8.0 (or any version below 7.70) is installed and NTLM authentication is in use, allowing credential theft via malicious shortcut files.
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 data7.70
Apply available SAP security patches for SAP GUI for Windows. Until patches are applied, consider disabling NTLM authentication, enabling SMB signing, and restricting user permissions to minimize exposure to credential theft attacks.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-32113 — 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-2023-32113 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