Skip to Content
Contact Us
Chat Now Chat Offline
Get live help and chat with an SAP representative.
Contact Us
E-mail us with comments, questions or feedback.
SAP Trust Center
A shield and a hand representing trust for SAP software

Securely configuring SAP Gateway and SAP Message Server

SAP is aware of recent reports about vulnerabilities in SAP Gateway and Message Server, however these have been patched by SAP a few years ago.  Security notes 821875, 1408081 and 1421005 released in 2009 and 2013 will protect the customer from these exploits. As always, we strongly advise our customers to apply these security notes immediately and ensure secure configuration of their SAP landscape.
SAP takes the security of customer data seriously. The recommendations published in the white papers Practical Guide for Securing SAP Solutions and Securing Remote Function Calls (RFC) emphasizes secure configuration of their SAP landscape. Customers can enable related security checks found in the EarlyWatch Alert (note 863362) and the SAP Security Optimization Services Portfolio.
SAP stands for secure and reliable software solutions. As the global leader in business software, SAP has based its development processes on a comprehensive security strategy (“Prevent – Detect – React”) across the enterprise that relies on trainings, tools and processes to enable the delivery of secure products and services. 

Processor-based vulnerabilities

At the beginning of 2018, with Spectre (and Meltdown), a new class of vulnerabilities was published. In the following months, new variants have been discovered and published under the same pseudonym. Ongoing research and publication of new vulnerabilities and attacks suggest that the topic will continue to be relevant in the future. The common denominator of these vulnerabilities is that they are mostly caused by the architectural (hardware) design of the CPU that affects nearly every computer chip manufactured in the last 20 years.
These vulnerabilities could, if exploited, allow attackers to gain access to data previously considered protected. Possible attacks are called side-channel attacks, in which the execution speed (timing) of certain operations could allow the removal of memory contents that are normally not accessible. From a security perspective, the concerns include the breaking of boundaries within virtualized environments.
SAP thoroughly investigates the impact of these vulnerabilities and is closely aligning with corresponding vendors, providers, and the Open Source community. SAP works on investigating if, where, and how our platforms, databases, applications, and cloud operations are affected.  
SAP is taking a proactive approach and is fixing potential flaws derived from hardware side-channel attacks without undue delay. You can find more information on our patching progress for our Cloud environments here (registration required). As a consumer of affected software and hardware, we largely depend on the availability of patches provided by respective vendors, providers, or the Open Source community. The schedule of applying appropriate patches is, to a large extent, determined by their availability.
SAP recommends that all customers carefully monitor and follow the advice on implementing security patches provided by hardware and operating system providers as soon as they become available. SAP will apply fixes to its cloud infrastructure without undue delay. SAP Global Security is constantly monitoring the situation.
Each variant was given its own CVE number (updated November 6, 2018):


Each of these vulnerability variants may be exploited to read confidential data such as CPU or kernel memory. The level of criticality and potential for exploitation differs between each of the variants. 
Further vendor information about before mentioned security vulnerabilities, resources and responses:
Please note that SAP is not liable for any content on these external sites.
Back to top