It is important to note that all SAP HANA Appliances are shipped by default with Operating Systems containing vulnerable versions of the library, therefore the base OS of the appliances must
be updated. One example of this is the SAP HANA One hosted in Amazon AWS
, as this image is delivered with the vulnerable library.
Last week a new vulnerability was reported, affecting the GNU C library (glibc). This vulnerability affects a wide range of Linux distributions, among which are some supported by SAP products as stated in SAP Note 171356.
It’s important to understand that even though this vulnerability does not directly affect any SAP application, it affects a lower layer, the operating system, allowing any application to potentially use the vulnerable function.
The following list details the OS that were reported as vulnerable and are supported by SAP, therefore there could be SAP applications running on top of the following vulnerable operating systems
The world of profile parameters in SAP is vast and complicated as a user can change the entire behavior of the SAP by modifying some of these parameters.
But just when we thought that we knew everything about profile parameters, we recently discovered something very interesting.
SAP Security Note 1979454 is related to a vulnerability in transaction SHDB (a very sensitive transaction since it’s used to create recordings) which introduced a new profile parameter called “bdc/shdb/auth_check”.
The problem with SHDB is that it wasn’t checking any authorization object besides from the S_TCODE, and a user with access only to the transaction could see any recording made by any user. If the user recorded a user creation the password would be shown in plain text. To mitigate this risk an authority check was introduced inside the programs, which would check for the authorization object S_BDC_MONI. However to enable this check, the parameter bdc/shdb/auth_check needs to be set to TRUE.
While going through the correction instructions for this note, we noticed that there wasn’t an update for the SAP Kernel (whenever a new profile parameter is introduced, there should be an update to the Kernel), so we decided to test the correction instructions to see how this parameter worked.
As we enter the New Year, there is a lot to look back on that has gotten Onapsis to where it is today.
The security industry has never been more complex, and as the need for reliable business-critical application security solutions increases, Fortune 500 companies are looking for a reliable solution they can trust to protect their processes and data running on SAP. In 2014, Onapsis established itself as the defacto solution to solve the most pressing SAP security and compliance challenges. After receiving funding in June from .406 Ventures and Endeavor, we have been able to double-down our investment in R&D to enhance our product offerings and launch the Onapsis Security Platform. We were also able to expand our global sales and marketing efforts to drive rapid growth. Fast forward 6 months later and we are well positioned and ready to see what 2015 has in store for the Onapsis team and the market we serve!
NEW NOTE (January 21, 2015)
: Note 2120370
has been released after the official SAP post of January 12nd. The note extends the security note 2001109
, covering further affected releases (BI 4.1 SP04 & BI 3.1 Patch 6.5).UPDATE (January 19, 2015)
: Note 1951171
has been rereleased translated into English, since it was originally published in German.
NEW NOTE (January 14, 2015)
: Note 1964201
has been released after the official SAP post of January 12nd. The note fixes a directory traversal in INTRASTAT module.
SAP is a complex and ever changing system, whether because of changes introduced to SAP implementation to better suit the business, or through the application of Security Notes (Patches) to ensure that newly disclosed vulnerabilities are mitigated.
In order to provide a predictable and scheduled flow of vulnerability mitigation information and security patches, SAP releases the major part of their latest Security Notes information on the second Tuesday of every month. Due to this regular disclosure of new security issues that could potentially weaken the security of SAP systems within an organization, it’s highly recommended to carry out periodic assessments on a monthly basis at the very least.
At Onapsis we are very concerned about our client’s SAP system security and the state of SAP security in general. To assist our customers, we perform a detailed analysis of the monthly SAP Security Notes as soon as they are published. The goal of this is to provide SAP clients with detailed information about the newly released notes and vulnerabilities affecting their SAP systems, and to help guide their testing of these systems within their organization.
Between the last SAP Security Tuesday and the notes published in January, there were 19 SAP Security notes (taking into account 7 Support Packages and 12 Patch Day Notes). There were notes published by external security researchers from which, Onapsis Research Labs reported SAP Security Note 2109565 by researchers Sergio Abraham, Nahuel D. Sánchez and Fernando Russ.
The plot graph illustrates the distribution of CVSS scores across the Security Notes released. The only notes taken into account were the ones for which SAP set a CVSS (6 out of the 19 SAP Security Notes). As it’s represented in the graph, the SAP Security Notes range values go from 4.9 to 8.5 with a median of 6.0.
As cyber-threats become more advanced, organizations face a constant dilemma: how to best implement a comprehensive security strategy that covers all areas of the business including critical infrastructure and applications. We hear from many security professionals that their SAP applications and systems are “covered” because they have a firewall and SAP systems sit inside the perimeter. After all, anything inside the firewall is safe from attacks right?
Security professionals that are true thought leaders have long abandoned this notion. In fact, most thought leaders have been able to connect the dots on the reasons why they have to include SAP applications into their security strategy. This type of thought leadership can be summed up in a quote from one of our newly appointed Board of Advisors, Renee Guttmann, Office of the CISO from Accuvant:
“There is a profound transformation taking place in application security right now …..Enterprises across the globe are committing to invest in, and protect, mission-critical applications, and this commitment needs to go beyond technology alone.”
2014 has been an incredible year for SAP security. Advanced threats targeting SAP systems that run business-critical applications are rising at an alarming rate. This year alone there have been 391 security notes to date, with 46% ranking as ‘high priority’ vulnerabilities. Out of these, our Research Labs reported 44 new vulnerabilities and 35 advisories affecting SAP platforms and related products such as SAP HANA, BusinessObjects, and SAP Business Suite running CRM and ERP. The latest two security advisories (fixed by notes 2039905 and 1979454) identified from our research labs include high-profile risk threats revealing that unauthorized users could access business-critical applications leveraging SAP BusinessObjects and SAP BASIS. This is a clear reminder of how key systems are constantly vulnerable to attack, and shows the importance of having a proactive plan in place before at attack occurs.
High-profile risk threats identified by Onapsis Research Labs experts reveals that unauthorized users could access business-critical applications leveraging SAP BusinessObjects
SAP is a complex and ever changing system, whether because of changes introduced to your SAP implementation to better suit your business or through the application of Security Notes (Patches) to ensure that newly disclosed vulnerabilities are mitigated.
In order to provide a predictable and scheduled flow of vulnerability mitigation information and security patches, SAP releases the major part of their latest Security Notes information on the second Tuesday of every month. Due to this regular disclosure of new security issues that could potentially weaken the security of SAP systems within an organization, it’s highly recommended to carry out periodic assessments on a monthly basis at least.
At Onapsis we are very concerned about our client’s SAP system security and also the state of SAP security in general, so to assist our customers, we perform a detailed analysis of the monthly SAP Security Notes as soon as they are published. The goal of this is to provide SAP clients with detailed information about the newly released notes and vulnerabilities affecting their SAP systems and help guide their testing of these systems within their organization.
Between the last published SAP Security Tuesday and today, there were 28 SAP Security notes published by SAP (taking into account 3 Support Packages and 25 Patch Day Notes).
The plot graph illustrates the distribution of CVSS scores across the Security Notes released in December. The only notes taken into account to build it, were the ones to which SAP set a CVSS (14 out of the 28 SAP Security Notes). As you may observe in the graph, the SAP Security Notes this month have a range of values from 1.5 to 7.5 with a median of 3.9.
As most users of SAPGUI know, the application keeps a record of the values that are entered in each field. In the case of having to repeat the same entries multiple times, this is of course a great feature… or maybe not?
Let’s analyze this from a security viewpoint. There are two main questions to ask:
- What is being recorded in the history?
- Is the history record safely-guarded so none but SAPGUI can access it?
For the first question, we clearly don’t want to have sensitive data lying somewhere around our computers, and in an ERP environment, there is a lot of sensitive data stored. For example, information such as passwords (keep calm, hidden fields where you only see ‘***’ instead of letters do not get recorded), money amounts, bank account numbers, etc. may be being recorded in the history.
Now let’s dive into the second question. Is this information safely guarded? Here the answer is simply “no”. It doesn’t matter whether you are using SAPGUI in Unix or Windows, the recording mechanism changes, but it’s very easy to access and read your history knowing which files to look at.
Today’s post will be focused on analyzing the inner workings of the SAP CODVN H algorithm.
Before jumping into the algorithm’s details I will highlight the most important features. For more information you can refer to the SAP security note 991968. The algorithm provides the following capabilities:
- Support for multiple hashing algorithms (for the time being only salted SHA-1).
- Supported password length up to 40 characters.
- Upper and lower case passwords supported.
- UTF-8 support.
- Random salt, length can be configured.
Last week we were doing some tests on the HANA XS engine trying to understand how an attacker could bypass the XSS filter provided by the ICM.
For what purpose?
As discussed in previous post, a Cross Site Scripting attack could be more effective than a SQL injection due to the SAP HANA inherent design. Continue reading