dbcve.org
Abap PlatformApplication · Sap

CVE-2023-29110

MEDIUM · 5.4 CVSS v3.1 Published 2023-04-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
The SAP Application Interface (Message Dashboard) - versions AIF 703, AIFX 702, S4CORE 100, 101, SAP_BASIS 755, 756, SAP_ABA 75C, 75D, 75E, application allows the usage HTML tags. An authorized attacker can use some of the basic HTML codes such as heading, basic formatting and lists, then an attacker can inject images from the foreign domains. After successful exploitations, an attacker can cause limited impact on the confidentiality and integrity 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 confidence

This is a stored HTML injection and potential Cross-Site Scripting (XSS) vulnerability in the SAP Application Interface Message Dashboard. An authenticated attacker can inject arbitrary HTML tags (headings, formatting, lists) and external images into the dashboard, potentially executing JavaScript or stealing session information through injected content.

MitigationApply the relevant SAP security patches for the affected versions (AIF 703, AIFX 702, S4CORE 100/101, SAP_BASIS 755/756, SAP_ABA 75C/75D/75E). Until patches are applied, implement server-side input validation and output encoding to sanitize HTML input in the Message Dashboard.

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
Abap PlatformApplication
Affected:= 75c= 75d= 75e
Application Interface FrameworkApplication
Affected:= aif_703= aifx_702
BasisApplication
Affected:= 755= 756
S4coreApplication
Affected:= 100= 101

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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

  1. Check SAP_BASIS version
    Execute SM51 to view the SAP system release, or use transaction SE11 to check table SAPCVERSIONS or run 'SWI5' to check installed software components. Look for SAP_BASIS versions 755 or 756.
    Affected if SAP_BASIS version is 755 or 756 (the only versions listed as affected)
  2. Check SAP ABAP Platform version
    Use transaction SPAM or SAINT to view the Support Package level, or check transaction SM37 for kernel version. Look for versions 75c, 75d, or 75e.
    Affected if SAP ABAP Platform version is 75c, 75d, or 75e (the only versions listed as affected)
  3. Verify SAP Application Interface Framework (AIF) installation
    Use transaction SAINT or SPAM to check installed software components. Look for AIF (AIF_703) or AIFX (AIFX_702) components.
    Affected if AIF component version is aif_703 or aifx_702 (the only versions listed as affected)
  4. Confirm S4CORE version if applicable
    For S/4HANA systems, use transaction SPAM or execute report RS Components to check S4CORE versions 100 or 101.
    Affected if S4CORE version is 100 or 101 (the only versions listed as affected)
  5. Verify Message Dashboard access and usage
    Use transaction /AIF/CONT to access the Application Interface Framework. Check if the Message Dashboard feature is enabled or accessible by navigating to the AIF transaction /AIF/ERR or /AIF/XI_MSG_MONITOR.
    Affected if The AIF Message Dashboard is accessible and in use (the vulnerable component)

The environment is affected if it runs any of the vulnerable SAP_BASIS (755/756), SAP_ABAP_PLATFORM (75c/75d/75e), AIF (aif_703/aifx_702), or S4CORE (100/101) versions AND has the Application Interface Framework Message Dashboard enabled and accessible.

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 the relevant SAP security patches for the affected versions (AIF 703, AIFX 702, S4CORE 100/101, SAP_BASIS 755/756, SAP_ABA 75C/75D/75E). Until patches are applied, implement server-side input validation and output encoding to sanitize HTML input in the Message Dashboard.

Fix this in Abap Platform Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-29110 — 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-29110 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