dbcve.org
Business Objects Business Intelligence PlatformApplication · Sap

CVE-2023-23856

MEDIUM · 5.4 CVSS v3.1 Published 2023-02-14
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
In SAP BusinessObjects Business Intelligence (Web Intelligence user interface) - version 430, some calls return json with wrong content type in the header of the response. As a result, a custom application that calls directly the jsp of Web Intelligence DHTML may be vulnerable to XSS attacks. On successful exploitation an attacker can cause a low impact on 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

In SAP BusinessObjects BI platform version 430, the Web Intelligence DHTML interface returns JSON responses with incorrect content-type headers (likely text/html or missing entirely). This causes browsers to potentially interpret the JSON payload as HTML, enabling reflected XSS attacks when a user accesses malicious links or custom applications consume these endpoints.

MitigationApply SAP security patches for CVE-2023-23856; alternatively, audit and修正 the affected JSP files to ensure all JSON responses include the proper 'Content-Type: application/json' header.

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
Business Objects Business Intelligence PlatformApplication
Affected:= 430

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. Confirm SAP BusinessObjects BI Platform version
    Check the installed version of SAP BusinessObjects Business Intelligence Platform. Typically found in the SAP BusinessObjects installation directory, system information, or SAP LMDB. Look for version 430 specifically.
    Affected if The installed version is exactly 430
  2. Verify Web Intelligence DHTML interface is accessible
    Check if the Web Intelligence DHTML interface is enabled and accessible. This is typically accessed via URLs containing /biprws/ or /webi/ paths under the BusinessObjects enterprise context.
    Affected if Web Intelligence DHTML interface is enabled and accessible to users
  3. Inspect Content-Type header of JSON responses
    Make an authenticated HTTP request to a Web Intelligence DHTML endpoint that returns JSON data (such as document lists or report data endpoints). Inspect the HTTP response headers, specifically the Content-Type header.
    Affected if The Content-Type header is missing, set to text/html, or any non-application/json value when JSON data is returned
  4. Check for reflected XSS vulnerability in JSON endpoints
    Send a crafted request with a test payload in a parameter to Web Intelligence JSON endpoints and examine if the payload is reflected in the response without proper encoding, particularly when Content-Type is incorrect.
    Affected if User-supplied input is reflected in the response unescaped and the Content-Type header is not application/json

A user is affected if they run SAP BusinessObjects BI Platform version 430 with Web Intelligence DHTML interface enabled and the endpoint returns JSON responses with Content-Type headers that are missing, text/html, or non-application/json, allowing potential XSS via malicious links or applications consuming these endpoints.

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 patches for CVE-2023-23856; alternatively, audit and修正 the affected JSP files to ensure all JSON responses include the proper 'Content-Type: application/json' header.

Fix this in Business Objects Business Intelligence Platform Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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