CVE-2025-42978

The widely used component that establishes outbound TLS connections in SAP NetWeaver Application Server Java does not reliably match the hostname that is used for the connection against the wildcard hostname defined in the received certificate of remote TLS server. This might lead to the outbound connection being established to a possibly malicious remote TLS server and hence disclose information. Integrity and Availability are not impacted.

Weakness

The product establishes a communication channel to handle an incoming request that has been initiated by an actor, but it does not properly verify that the request is coming from the expected origin.

Potential Mitigations

• Use a mechanism that can validate the identity of the source, such as a certificate, and validate the integrity of data to ensure that it cannot be modified in transit using an Adversary-in-the-Middle (AITM) attack.
• When designing functionality of actions in the URL scheme, consider whether the action should be accessible to all mobile applications, or if an allowlist of applications to interface with is appropriate.

Related Attack Patterns

• https://cwe.mitre.org/data/definitions/500.html
• https://cwe.mitre.org/data/definitions/594.html
• https://cwe.mitre.org/data/definitions/595.html
• https://cwe.mitre.org/data/definitions/596.html

References

• https://me.sap.com/notes/3557179
• https://url.sap/sapsecuritypatchday