CVE-2023-49581
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 and SAP GUI for Java allow an unauthenticated attacker to access information which would otherwise be restricted and confidential. In addition, this vulnerability allows the unauthenticated attacker to write data to a database table. By doing so the attacker could increase response times of the AS ABAP, leading to mild impact on availability.
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 and SAP GUI for Java contain an access control vulnerability that allows unauthenticated attackers to access restricted/confidential information and write arbitrary data to a database table. This can degrade AS ABAP response times, impacting system availability.
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= 700= 731= 740= 750CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L
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 for Windows, go to Help > About SAP Logon, or check the version from the executable properties (right-click on saplogon.exe > Properties > Details). Also check in Windows Registry under HKLM\SOFTWARE\SAP\SAP GUI\VersionAffected if The installed version equals 700, 731, 740, or 750
-
Identify SAP GUI for Java versionOpen SAP GUI for Java, go to Help > About, or run 'java -jar sapgui.jar -version' if available from command line. Check the installation directory for version information in the launcher configurationAffected if The installed version equals 700, 731, 740, or 750
-
Confirm SAP GUI version against affected rangesCompare the identified version number (e.g., 7.50, 7.40, 7.31, 7.00) to the affected versions list. Note that version formats may vary (e.g., 7.50 vs 750 vs 7.5)Affected if The exact version matches one of the affected versions 700, 731, 740, or 750 (or their decimal equivalents)
-
Verify if SAP GUI connects to vulnerable ABAP systemsReview SAP Logon pad entries or SAP GUI for Java connection definitions to identify connected ABAP systems. Check the connected system versions by logging into each system and running transaction SM51 or checking system informationAffected if The connected SAP NetWeaver ABAP system is version 700, 731, 740, or 750
A user is affected if their installed SAP GUI for Windows or Java version is 700, 731, 740, or 750 (or equivalent) and connects to an affected ABAP system, enabling unauthenticated access to restricted data.
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 SAP security patches for affected SAP GUI for Windows and SAP GUI for Java versions. Verify that unauthorized read/write access is no longer possible after patching.
- Consultation12.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 $11,520.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-49581 — 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-49581 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