dbcve.org
Application InterfaceApplication · Sap

CVE-2023-29112

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 Monitoring) - versions 600, 700, allows an authorized attacker to input links or headings with custom CSS classes into a comment. The comment will render links and custom CSS classes as HTML objects. 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 · high confidence

This is a stored Cross-Site Scripting (XSS) vulnerability in SAP Application Interface's Message Monitoring component (versions 600 and 700). An authenticated attacker can inject malicious links or headings with custom CSS classes into comments, which then render as HTML objects in the application's user interface, allowing execution of potentially malicious content in other users' browsers.

MitigationApply the relevant SAP security patch/note to implement proper input validation and output encoding for the comment field in Message Monitoring. Until patched, monitor for suspicious comments containing custom CSS or non-standard HTML elements.

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
Application InterfaceApplication
Affected:= 600= 700

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. Identify SAP Application Interface version
    Access the SAP system landscape transaction (e.g., SLM or system information page) or check the SAP Note/About section of the Application Interface to determine the installed version number.
    Affected if The installed version is exactly 600 or exactly 700.
  2. Locate Message Monitoring component
    Navigate to the SAP Application Interface framework and access the Message Monitoring function. This is typically found under the interface monitoring or message monitoring tile in the SAP Fiori launchpad or SAP GUI transaction.
    Affected if The Message Monitoring component is accessible and in use.
  3. Examine comment fields for HTML injection vectors
    Open the Message Monitoring details view where comments can be added to messages. Inspect any existing comments by viewing the page source or using browser developer tools to see if custom CSS classes or HTML elements are being rendered.
    Affected if Comments render as HTML objects and accept custom CSS classes or non-standard HTML tags (like custom-class links or styled headings).
  4. Inspect stored comments for malicious content
    Review all comments in the Message Monitoring database or UI for suspicious patterns: custom CSS classes (style=), JavaScript event handlers (onclick=, onload=), iframe/embed tags, or non-standard HTML elements that could execute code.
    Affected if Any stored comments contain custom CSS definitions, JavaScript event handlers, or non-standard HTML elements that execute in other users' browsers.

A user is affected if they are running SAP Application Interface version 600 or 700 with the Message Monitoring component enabled, and if comment fields in Message Monitoring render HTML or accept custom CSS classes without sanitization.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the relevant SAP security patch/note to implement proper input validation and output encoding for the comment field in Message Monitoring. Until patched, monitor for suspicious comments containing custom CSS or non-standard HTML elements.

Recommended fix Moderate confidence

Upgrade to a version higher than 700 (e.g., latest available version of SAP Application Interface)

  1. Check SAP Support Portal (launchpad.support.sap.com) for the specific Security Note related to CVE-2023-29112
  2. Review the security note to identify the required patch or kernel update
  3. In a non-production environment first, test the patch to ensure compatibility with your system landscape
  4. Schedule a maintenance window for patch deployment
  5. Apply the SAP Security Note/patch following SAP's standard patching procedures
  6. After applying the patch, verify that the XSS vulnerability is remediated by testing the Message Monitoring functionality
  7. Confirm custom CSS classes and untrusted HTML are no longer rendered in comments
Caveat Review SAP release notes for the target version to check for any compatibility considerations or deprecated functionality

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Application Interface Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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