dbcve.org
Graphical User InterfaceApplication · Sap

CVE-2023-49580

HIGH · 7.3 CVSS v3.1 Published 2023-12-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
SAP GUI for Windows and SAP GUI for Java - versions SAP_BASIS 755, SAP_BASIS 756, SAP_BASIS 757, SAP_BASIS 758, allow an unauthenticated attacker to access information which would otherwise be restricted and confidential. In addition, this vulnerability allows the unauthenticated attacker to create Layout configurations of the ABAP List Viewer and with this causing a mild impact on integrity and availability, e.g. also increasing the response times of the AS ABAP.

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 confidence

This vulnerability in SAP GUI for Windows and Java (versions SAP_BASIS 755-758) allows unauthenticated attackers to access restricted confidential information and create/modify ABAP List Viewer layout configurations, causing integrity and availability impacts including degraded AS ABAP response times.

MitigationApply SAP security notes/patches for the affected SAP_BASIS versions to restrict access to confidential information and prevent unauthorized ABAP List Viewer layout configuration changes.

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
Graphical User InterfaceApplication
Affected:= sap_basis_755= sap_basis_756= sap_basis_757= sap_basis_758

CVSS 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
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed SAP_BASIS version
    Query the SAP system for the SAP_BASIS version using transaction code SM51, or check the SAP kernel version via the SAP MMC or /usr/sap/<SID>/SYS/exe/run/sapexepatchlist (Linux/Unix). Compare this version number to the affected range: 755, 756, 757, or 758.
    Affected if The installed SAP_BASIS version matches 755, 756, 757, or 758.
  2. Confirm SAP GUI client deployment
    Identify whether SAP GUI for Windows or SAP GUI for Java is installed and in use in the environment. Check installed programs on Windows clients or the Java client deployment status.
    Affected if SAP GUI for Windows or Java is deployed and connects to the affected SAP system.
  3. Verify ABAP List Viewer access
    Determine if the ALV (ABAP List Viewer) component is accessible. This can be checked by reviewing SAP GUI transaction codes that use ALV (such as SE16, SE11, MB1A, etc.) and whether they are accessible to users without additional authorization controls.
    Affected if ALV functionality is accessible without proper authentication or authorization restrictions.
  4. Assess network exposure of SAP GUI services
    Review whether SAP GUI ports (typically 3200-3209 for SAP GUI, 3300-3399 for SAP Message Server) are exposed to untrusted networks or the internet. Check firewall rules and network segmentation around SAP application servers.
    Affected if SAP GUI services are reachable from untrusted networks, enabling unauthenticated attackers to exploit the vulnerability.

A system is affected if it runs SAP_BASIS versions 755-758, has SAP GUI for Windows or Java deployed, and allows unauthenticated network access to ALV-related functionality.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply SAP security notes/patches for the affected SAP_BASIS versions to restrict access to confidential information and prevent unauthorized ABAP List Viewer layout configuration changes.

Fix this in Graphical User Interface Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-49580 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-49580 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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