VulnerabilityPublished 8 Jul 2025

CVE-2025-42954: SAP NetWeaver Business Warehouse (CCAW application) · Loop with Unreachable Exit Condition

Affects SAP NetWeaver Business Warehouse (CCAW application)Source CVE Database V5

Not known to be exploited · CVSS 2.7 Low.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

2.7Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 8 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Mavencom.sap.netweaver/business-warehouse-ccaw`pkg:maven/com.sap.netweaver/business-warehouse-ccaw`Other threats	Affected 200 – 816 17 affected builds	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate this vulnerability, European organizations should implement the following specific measures: 1) Restrict and monitor privileged access to SAP BW systems, ensuring that only authorized personnel can execute RFC calls. 2) Audit and review all RFC-enabled function modules to identify and control those that can be invoked without input parameters, applying stricter input validation where possible. 3) Implement resource usage monitoring and alerting on SAP BW servers to detect abnormal CPU spikes early, enabling rapid response to potential exploitation attempts. 4) Apply SAP security notes and patches promptly once available, as SAP is expected to release updates addressing this issue. 5) Use SAP's security configuration guides to harden the environment, including disabling unnecessary RFC modules and enforcing least privilege principles. 6) Conduct regular security training for administrators to recognize and prevent misuse of privileged functions. 7) Consider implementing runtime application self-protection (RASP) or similar technologies to detect and block anomalous function calls. These steps go beyond generic advice by focusing on controlling privileged access, input validation, and proactive monitoring tailored to the nature of this vulnerability.

Description

SAP NetWeaver Business Warehouse CCAW application allows a privileged attacker to cause a high CPU load by executing a RFC enabled function modules without any input parameters, which results in reduced performance or interrupted operation of the affected resource. This leads to low impact on availability of the application, there is no impact on confidentiality and integrity.

Impact

For European organizations utilizing SAP NetWeaver Business Warehouse, this vulnerability primarily threatens system availability. High CPU load induced by the vulnerability can degrade performance, slow down business-critical data processing, and potentially cause service interruptions. This can affect reporting, analytics, and decision-making processes dependent on SAP BW. Although the impact on confidentiality and integrity is null, availability issues can lead to operational disruptions, financial losses, and reputational damage, especially in sectors with stringent uptime requirements such as finance, manufacturing, and public services. Given that SAP BW is widely used across Europe in large enterprises and government agencies, the vulnerability could affect a broad range of organizations. However, exploitation requires privileged access, which limits the threat to insider threats or compromised privileged accounts. The absence of known exploits in the wild reduces immediate risk but does not eliminate the potential for future attacks. Organizations with automated or scripted RFC calls should be cautious, as these might inadvertently trigger the high CPU load condition.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Jul 2025, 00:58 UTC

WeaknessesCWE-835

Technical details

References

Community reviews

Related threats