dbcve.org
Business Objects Business Intelligence PlatformApplication · Sap

CVE-2024-41730

CRITICAL · 9.8 CVSS v3.1 Published 2024-08-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
High EPSS Remotely reachable No privileges 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
In SAP BusinessObjects Business Intelligence Platform, if Single Signed On is enabled on Enterprise authentication, an unauthorized user can get a logon token using a REST endpoint. The attacker can fully compromise the system resulting in High impact on confidentiality, integrity and availability.

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 Business Intelligence Platform, when Single Sign-On (SSO) is enabled on Enterprise authentication, an unauthenticated attacker can obtain a valid logon token by exploiting a REST endpoint. This token allows full unauthorized access to the system, compromising confidentiality, integrity, and availability.

MitigationDisable SSO on Enterprise authentication until vendor patch is applied, or implement proper authentication validation on the vulnerable REST endpoint to prevent unauthorized token generation.

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:= enterprise_430= enterprise_440

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 installation
    Locate the SAP BusinessObjects installation directory (commonly under C:\Program Files\SAP BusinessObjects\ or /opt/sap/bobj/) and confirm the BI Platform is installed. Check for the 'lcm' or 'businessobjects' subdirectories.
    Affected if SAP BusinessObjects Business Intelligence Platform is not installed on the system.
  2. Determine installed BI Platform version
    Check the version of the installed SAP BusinessObjects BI Platform. Look for version information in the installation directory, typically in a version file or the，中央管理工具 (CMC) about page. Compare your version against the affected ranges: enterprise_430 and enterprise_440.
    Affected if The installed version is enterprise_430 or enterprise_440.
  3. Verify if SSO is enabled on Enterprise authentication
    Access the Central Management Console (CMC) or use the administration tools. Navigate to Authentication settings and check whether Single Sign-On (SSO) is enabled for Enterprise authentication. This is typically found under CMC > Authentication > Enterprise.
    Affected if SSO is enabled for Enterprise authentication - this is the required condition for the vulnerability to be exploitable.
  4. Check REST endpoint configuration for authentication validation
    Review the REST API configuration files in the BusinessObjects installation directory (commonly under webapps\BOE\WEB-INF\ or similar). Examine the REST endpoint authentication handling to determine if proper validation is implemented for token generation requests.
    Affected if The REST endpoint allows unauthenticated token generation without proper validation - indicates the vulnerability is present.

If the system runs SAP BusinessObjects BI Platform versions 430 or 440 with SSO enabled on Enterprise authentication, the environment is vulnerable to unauthenticated token generation via the REST endpoint.

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

Disable SSO on Enterprise authentication until vendor patch is applied, or implement proper authentication validation on the vulnerable REST endpoint to prevent unauthorized token generation.

Fix this in Business Objects Business Intelligence Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,300
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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