Advisory

SAP takes the security of its vast product portfolio very seriously and thus releases security fixes for vulnerabilities reported by external researchers and their customers every second Tuesday of the month.

SAP Note 3525794 was released on 11.02.2025 and deals with "[CVE-2025-0064] Improper Authorization in SAP BusinessObjects Business Intelligence platform (Central Management Console)" within BI/BO platform. We advice you to follow the instructions, to resolve missing authorization check with a high potential for exploitation in component BI-BIP-AUT.

According to SAP Security Advisory team a workaround does not exist. It is advisable to implement the correction as part of maintenance.

Missing authority checks are still the most common security defect related to authorizations in custom code. Since SAP uses an explicit authorization model, an authority checks must be coded in order to be executed. If an explicit check is not coded, all users have access. This type of vulnerability not only exists in SAP standard it also exists in customer coding. Check your custom developments for vulnerabilities that pose a risk to your systems. SecurityBridge helps detect code vulnerabilities before they are implemented in production.

Risk specification

SAP BusinessObjects Business Intelligence platform (Central Management Console) allows an authenticated attacker with administrative privileges to retrieve a secret passphrase, potentially enabling user impersonation within the system.

Solution

Administrators no longer have access to secret passphrases.

Affected System

SAP BusinessObjects Business Intelligence suite is an analytics platform allowing SAP customers to make better decisions based on their business data. SAP BI is a module meant for producing business insights and expands its power in combination with HANA DB and also exists as BW/4 HANA. Due to processing sensitive business data, the Data security is of utmost importance.

The advisory is valid for

ENTERPRISE 2025 ⁸
ENTERPRISE 430 ⁸¹

Releated advisories

Disclaimer

SecurityBridge takes the security of SAP products very seriously. We very much encourage the responsible disclosure of security vulnerabilities. If you have detected a vulnerability concerning one of the SAP software products – either in the latest or in a former product version follow the guidelines and processes in accordance with the SAP portal page “Report a Security Vulnerability to SAP”.

The advisories found within the SecurityBridge advisory are generated and continuously enriched by our Team at SecurityBridge and affiliated security consultants, partners, customers of the SecurityBridge Platform, SAP support, and advisory groups.

We do not disclose zero-day vulnerabilities unless a security patch has been made available to the public. In such case, the platform only provides details on which version or signature updates are available within the SecurityBridge platform in order to monitor or measure the vulnerability.

In accordance with SAP guidelines, SecurityBridge only discloses issues where the fixing security note has been released. The vulnerability platform makes no references to available exploits or Proof of Concepts (PoC). Advisories and vulnerabilities will always mention the fixing security note or hints to the corresponding SAP documentation.

SecurityBridge - Code vulnerabilty analysis

Secure code
Customer created code contains security risks. Use modern technologies to detect coding flaws mitigate unneccessary risks. Start to detect:

Open & Native SQL Injection
Potential backdoors
Insuffient authorization checks of user administration bypassed
Injections of operating system commands
and many more..

Start scanning for ABAP Code vulnerabilities

Follow @_securitybridge

Notifications

Affected system BI/BO platform

CVSS 8.7

Component BI-BIP-AUT

Patch Day2025-02

Released on2025/02/11

SAP Note 3525794

Workaround No

Advisory

Risk specification

Solution

Affected System

Disclaimer

_{Affected system}
BI/BO platform

_CVSS
8.7

_Component
BI-BIP-AUT

_{Patch Day}
2025-02

_{Released
on}
2025/02/11

_{SAP Note}
3525794

_Workaround
No