dbcve.org
Businessobjects Business Intelligence PlatformApplication · Sap

CVE-2023-24530

CRITICAL · 9.1 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 →
97/100
Remediation priority · Urgent
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
SAP BusinessObjects Business Intelligence Platform (CMC) - versions 420, 430, allows an authenticated admin user to upload malicious code that can be executed by the application over the network. On successful exploitation, attacker can perform operations that may completely compromise the application causing high impact on confidentiality, integrity and availability 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

In SAP BusinessObjects Business Intelligence Platform CMC versions 420 and 430, an authenticated administrator can upload malicious code through the CMC interface, which the application then executes over the network. This leads to full compromise of confidentiality, integrity, and availability.

MitigationRestrict and monitor admin-level access to CMC, implement strict upload controls and validation, apply vendor patches when available, and segment the application network to limit exposure.

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 Intelligence PlatformApplication
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
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

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 Platform. In the Central Management Console (CMC), go to 'About SAP BusinessObjects' or check the system information page. Alternatively, check the version file in the installation directory or use the SAP BusinessObjects installation diagnostics.
    Affected if The installed version is exactly 420 or exactly 430.
  2. Confirm CMC interface is accessible
    Verify whether the Central Management Console (CMC) web interface is accessible on the network. Check if port 8080, 8443, or the configured HTTP/HTTPS port for CMC is exposed and reachable.
    Affected if The CMC interface is accessible over the network and does not have strict network segmentation restricting access to authorized admin stations only.
  3. Identify administrator accounts in CMC
    In the CMC interface, navigate to 'Users' or 'Administrators' section to list accounts with administrator privileges. Check for any default or unused admin accounts that may exist.
    Affected if There are administrator accounts configured in CMC, particularly default accounts or accounts with elevated privileges that could be exploited if compromised.

If the installed version is exactly 420 or 430, the CMC interface is network-accessible, and administrator accounts exist in the system, then the environment is potentially affected by CVE-2023-24530.

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

Restrict and monitor admin-level access to CMC, implement strict upload controls and validation, apply vendor patches when available, and segment the application network to limit exposure.

Recommended fix Moderate confidence

SAP BusinessObjects BI Platform version higher than 430 (refer to SAP Security Note for exact fixed version)

  1. Check the official SAP Security Note for CVE-2023-24530 on the SAP Support Portal (launchpad.support.sap.com) to obtain the specific patch or updated version number
  2. Identify the exact patch level of your current SAP BusinessObjects BI Platform installation (420 or 430.x)
  3. Apply the security patch provided by SAP, or upgrade to the fixed version specified in the SAP Security Note
  4. After applying the patch, verify the fix by checking that file upload functionality in the Central Management Console (CMC) properly restricts malicious file types
  5. Restart affected services as required by the SAP patch documentation
Caveat Review SAP release notes for potential configuration or compatibility changes between versions; test upgrade in non-production environment first

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

Fix this in Businessobjects Business Intelligence 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-24530 — 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-24530 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