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 3426825 was released on 11.02.2025 and deals with "[CVE-2025-23191] Cache Poisoning through header manipulation vulnerability in SAP Fiori for SAP ERP" within ABAP. We advice you to follow the instructions, to resolve insufficient security function with a low potential for exploitation in component OPU-GW-COR.

According to SAP Security Advisory team a workaround does not exist. It is advisable to implement the correction as monthly patch process.

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 Gateway enables an authenticated attacker to inject and store arbitrary URLs within the OData metadata schema file, potentially redirecting other users to a malicious link controlled by the attacker.

Solution

The OData metadata no longer stores host and port information.

Affected System

The advisory 3426825 describes a problem within an ABAP based systems of a specific version. Affected versions are described below. ABAP software is deployed in various software components and is widely used within the SAP product portfolio.

SAP NetWeaver Application Server (formally known as SAP Web Application Server) is a building block of SAP NetWeaver. It is the foundation for most software products developed by SAP SE. SAP NetWeaver systems exist with Java and/or ABAP stacks. The advisory could be relevant for single and dual-stack ABAP installations.

The advisory is valid for

SAP_GWFND 740 ²
SAP_GWFND 750
SAP_GWFND 751
SAP_GWFND 752
SAP_GWFND 753
SAP_GWFND 754
SAP_GWFND 755
SAP_GWFND 756
SAP_GWFND 757
SAP_GWFND 758

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^{for SAP©}
empowers security teams with forward-looking, high fidelity, adversary-focused intelligence and actionable events from SAP Netweaver based systems.

Follow @_securitybridge

Notifications

Affected system ABAP

CVSS 3.1

Component OPU-GW-COR

Patch Day2025-02

Released on2025/02/11

SAP Note 3426825

Workaround No

Advisory

Risk specification

Solution

Affected System

Disclaimer

_{Affected system}
ABAP

_CVSS
3.1

_Component
OPU-GW-COR

_{Patch Day}
2025-02

_{Released
on}
2025/02/11

_{SAP Note}
3426825

_Workaround
No