dbcve.org
Businessobjects Business IntelligenceApplication · Sap

CVE-2023-31404

MEDIUM · 5.0 CVSS v3.1 Published 2023-05-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
56/100
Remediation priority · Elevated
Remotely reachable 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
Under certain conditions, SAP BusinessObjects Business Intelligence Platform (Central Management Service) - versions 420, 430, allows an attacker to access information which would otherwise be restricted. Some users with specific privileges could have access to credentials of other users. It could let them access data sources which would otherwise be restricted.

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 an information disclosure vulnerability in SAP BusinessObjects BI Platform's Central Management Service (CMS). Users with specific privileges can access credentials of other users, allowing them to bypass access controls and reach data sources that should be restricted.

MitigationApply the relevant SAP security patch when available. In the interim, review and restrict privileged user accounts, audit user access permissions, and monitor for unauthorized credential access.

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
Businessobjects Business IntelligenceApplication
Affected:= 420= 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
None
Scope
Changed
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/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 BusinessObjects BI Platform version
    Check the installed version of SAP BusinessObjects Business Intelligence through the Central Management Console (CMC) under 'About' or via the 'cmdb' command-line tool. Alternatively, check the installation directory for version files or the SAP BusinessObjects installation logs.
    Affected if The installed version is exactly 420 or exactly 430, as these are the affected versions listed.
  2. Confirm Central Management Service (CMS) is running
    Verify that the Central Management Service is active. In the CMC, navigate to the 'Servers' node and check the status of the CMS service. Alternatively, use the SAP BusinessObjects command-line tools to query the server status.
    Affected if CMS is running and the application version is 420 or 430, as the vulnerability exists in the CMS component.
  3. Review user account privileges in CMC
    Open the Central Management Console and navigate to 'Users and Groups'. Examine user accounts, particularly those with privileged access such as 'Administrator' or accounts with 'Full Control' permissions. Check which users have the ability to manage or view other user accounts.
    Affected if Privileged user accounts exist in the system, as the vulnerability allows users with specific privileges to access credentials of other users.
  4. Inspect audit logs for credential access events
    Access the SAP BusinessObjects Audit log files, typically located in the installation directory under '/logging' or through the CMC's 'Audit' node. Search for events related to user credential retrieval, password viewing, or authentication token access.
    Affected if Audit logs show any instances of users accessing credentials outside their normal scope, indicating exploitation of this vulnerability.
  5. Check data source connection configurations
    Review the data source connections defined in the CMC under 'Data Source Connections' or 'OLAP Connections'. Verify whether credentials stored for these connections are visible to users beyond those who should have access.
    Affected if Multiple users have visibility into data source credentials that they should not have access to, which would indicate the vulnerability has been exploited.

You are affected if your SAP BusinessObjects BI Platform is version 420 or 430 AND the Central Management Service is running, since the vulnerability allows privileged users to access credentials of other users through CMS.

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 patch when available. In the interim, review and restrict privileged user accounts, audit user access permissions, and monitor for unauthorized credential access.

Fix this in Businessobjects Business Intelligence Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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