Unauthenticated SQL Injection and DoS in JobBean P4 service

Impact On Business

An unauthenticated attacker with access to the P4 port of a java-based SAP solution, would be able to read any table from the database, modify sensitive information and/or cause a Denial of Service against the targeted system. As a consequence, sensitive information could be leaked even allowing an anonymous external attacker to escalate their attack from a partial compromise to a full compromise of the system.

This vulnerability is part of a bigger family named P4CHAINS. This group of bugs may cause more serious consequences and expose systems to worst scenarios. For more information please visit: https://onapsis.com/blog/p4chains-vulnerabilities-where-the-risk-from-the-whole-is-greater-than-the-sum

Affected Components Description

The Process Integration / Process Orchestration is based on the interchanging of PI messages in order to carry out it main tasks.This messaging framework is implemented inside the MESSAGING SYSTEM SERVICE.

Vulnerability Details

P4 is a proprietary protocol implemented by SAP in the NetWeaver JAVA stack. In a nutshell, this protocol is based on RMI and CORBA technologies with the goal of providing features for interchanging objects in a remote way. Through, the P4 interface it is possible to access to a bunch of exposed services. All those services are implemented using JAVABeans technology.

Within that list of services, JobBean was found. This service seems to implement the all functionalities related with administrating and jobs and their properties. The interface that the object implemented was exposing several functions, all accessible without authentication.

By analyzing these exposed functionalities it was possible to find injection points where user controlled data would be appended to SQL statements without prior sanitization. Additionally, other specific function would allow to provide parameters that could make the system to hang, causing a complete DoS.

Solution

SAP has released SAP Note 3267780 which provides patched versions of the affected components.

The patches can be downloaded from https://launchpad.support.sap.com/#/notes/3267780

Onapsis strongly recommends SAP customers to download the related security fixes and apply them to the affected components in order to reduce business risks.

Report Timeline

• 10/28/2022: Vulnerability reported to vendor.
• 10/31/2022: Vendor provide incident number.
• 11/03/2022: SAP asked for clarification about CVSS vector.
• 11/03/2022: Onapsis sends justification for each part of the vector that was challenged.
• 11/16/2023: SAP asked for clarification about CVSS vector.
• 11/17/2023: Conversation between SAP and Onapsis going back and forward.
• 12/13/2022: Patch released.

---

REFERENCES

• Onapsis blogpost: https://onapsis.com/blog/sap-security-patch-day-january-2023
• CVE Mitre: https://nvd.nist.gov/vuln/detail/CVE-2023-0017
• Vendor Patch: https://me.sap.com/notes/3267780/E
• Black Hat Talk: https://www.blackhat.com/us-23/briefings/schedule/#chained-to-hit-discovering-new-vectors-to-gain-remote-and-root-access-in-sap-enterprise-software-31340
• P4chains blogpost: https://onapsis.com/blog/p4chains-vulnerabilities-where-the-risk-from-the-whole-is-greater-than-the-sum