BlackHat EU 2010 Di Croce SAP Backdoors Slides

SAP Backdoors
A ghost at the heart of your business
Mariano Nuez Di Croce

[email protected]
April 14, 2010
Black Hat Europe 2010 Briefings
Disclaimer
This publication is copyright Onapsis SRL 2010 All rights reserved. This publication contains references to the products of SAP AG. SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius and other Business Objects products and services mentioned herein are trademarks or registered trademarks of Business Objects in the United States and/or other countries. SAP AG is neither the author nor the publisher of this publication and is not responsible for its content, and SAP Group shall not be liable for errors or omissions with respect to the materials.
SAP Backdoors Presentation
www.onapsis.com Onapsis S.R.L. 2010 All rights reserved
Who is Onapsis?
Specialized company focused in the Security of Business-critical Applications (SAP, Siebel, Oracle E-Business SuiteTM, JD Edwards ). Core business areas: Development of specialized security software solutions. Security consultancy services. Trainings on business-critical systems security.
Who am I?
Director of Research and Development at Onapsis. Degree in Computer System Engineering. Originally devoted to Penetration Testing and Vulnerability Research. Discovered vulnerabilities in Microsoft, Oracle, SAP, IBM, Speaker/Trainer at Black Hat, HITB, Sec-T, Hack.lu, DeepSec, Ekoparty..
SAP Backdoors Presentation www.onapsis.com Onapsis S.R.L. 2010 All rights reserved 3
Agenda
Introduction A Ghost in the User Master Backdoors in SAP Business Modules Backdoors in the Authentication Procedure Onapsis Integrity Analyzer for SAP Conclusions
Introduction
What is SAP?
Largest provider of business management solutions in the world. More than 140.000 implementations around the globe. More than 90.000 customers in 120 countries. Used by Fortune-500 world-wide companies, governmental organizations and defence facilities to run their every-day business processes. Such as Revenue / Production / Expenditure business cycles.
FINANCIAL PLANNING
TREASURY
PAYROLL
LOGISTICS
SALES
INVOICING
PRODUCTION
PROCUREMENT
BILLING
6
Backdoor special methods that are implemented in an information system, usually after an unauthorized compromise, with the purpose of securing future access to the system while attempting to remain undetected.
Why are SAP Backdoors special?

Backdoors have been known since the origins of computer systems. However, there is very little (no) public information about how they can affect SAP platforms. Not Public != Not currently being exploited The biggest mis-conception in the term SAP Security: SAP Security is much more than Segregation of Duties! Most standards & regulations still dont get it. Most Auditing companies still dont get it. Some customers still dont get it.
SoD is not enough to prevent Backdoors!

From the trenches:
During an assessment, a SoD compliant SAP system (which had costed $$$$^n to implement), could be remotely compromised in a matter of seconds through the exploitation of a vulnerability in a technological component. With that kind of privilege, a backdoor could have been installed.
Ok, but which is the real risk?
ESPIONAGE SABOTAGE FRAUD
10
The Initial Compromise

In order to install a backdoor, the attacker needs to compromise the system first, and obtain high privileges. The Threat Model map includes the following components:
SAP Business Application Layer SAP IT Application Layer Database Layer Operating System Layer
11
Wide Attack Surface

Due to intrinsic Trust relationships, a high-privileged takeover of one technological component results in a complete compromise of the whole platform. OS Administrator <==> DBA <==> SAP_ALL !!
Check the Onapsis Penetration Testing SAP Systems Presentation[1] for further insights.
12
A Ghost in the User Master
13
Welcome to the SAP world

You connect to your companys Production SAP system through SAPGUI. You have to specify access credentials: Client (logical independent unit in the SAP system) Username Password The system checks your saved password from the User Master. If your provided passwords matches the stored one access granted. You start performing business processes and making the company earn billions.
14
Oops! Downwards compatibility

SAP has implemented different password hashing mechanisms to make systems stronger (from 8-characters MD5 to 40-characters SHA-1) The problem happens when a weak system wants to connect with a strong one integration fails -> business fails. Workaround: By default, the User Master shall contain the downwards-compatible hashes, as well as the strong one. This opens room for several attacks. Check Onapsiss SAP Security In-Depth Publication, issue #2 [2]
Oops! Downwards compatibility

Which password hash to use for comparison? Controlled through profile parameter login/password_downwards_compatibility
Value 0 1 2 Impact Downwards-compatibility disabled. No weak hashes are generated. Downwards-compatibility enabled. Weak hashes generated for integration with older releases. Weak hashes not evaluated. If the logon attempt using the downwards-incompatible password fails, check if the downwards-compatible would work. Log and deny access. The same as with 2, but the logon is considered as successful. This is registered in the system log. The same as with 3, but no system log entry is written.
3 4
Parameter can be modified dynamically! (No SAP restart required)

Live demo
17
Protection / Countermeasure
Monitor the value of the specified profile parameter to detect insecure values. Implement a dedicated authorization group for U* tables. Check SAP Note 1023437.
18
Backdoors in SAP Business Modules
19
Welcome (back) to the SAP World

Once logged-in, you interact with the system running Transactions. In fact, you are running ABAP Programs/Reports. ABAP Programs can be divided in: Standard (Developed and Shipped by SAP A.G) Custom (Developed in-house by the company. Starts with Z* or Y*) Standard programs can be modified, but strongly discouraged. SSCR steps in =>You must ask SAP A.G for a special key. ABAP Programs are stored in the systems database. Table REPOSRC contains compressed source-code. Table REPOLOAD containst ABAP load (~ bytecode).
The Change and Transport System

Typical SAP system landscape:
Developments and changes can only be done in the DEV system. The PRD system is configured to block any attempt to modify programs directly in the system. Through this procedure, it is expected that the quality and availability of the SAP production systems is maximized.
Unauthorized modification of ABAP Programs directly in the Production System is possible.

SAPs Heart: The Database

Unauthorized modification at the SAP layer may be possible, but not trivial. What about the usually mis-configured-left-by-default-LANaccesible Database?? SAP + Oracle Authentication Weakness. Default SAP Database users credentials. Database exploits. The attacker can still get to the Database through the SAP system, due to the intrinsic Trust relationships! No CRC or signature check on the stored ABAP code. Simple SQL queries will do the trick!
Live demo
24
Backdoors in the Authentication Procedure
25
Protection for Critical ABAP Programs

Certain critical standard ABAP programs are protected to prevent access to their source code from the SAP System, i.e. using transaction SE80. Started researching on how this feature was implemented: REPOSRC.SQL = X ? No noticeable results. Special ABAP Magic String: *@#@@[SAP] If the source code contains the magic string, the SAP Kernel rejects access to the source code. However, there seems to be something else
SAPMSYST The SAPs Cop

Probably the most critical ABAP piece of code in an SAP system. Handles the User Authentication Procedure. This program is protected through a specific, hard-coded Kernel check! The check is performed on the ABAP programs name Bypass is possible by pivoting the program in the Database.
27
Live demo
28
Protection / Countermeasure
Its not possible to detect and protect against backdoors from within the SAP system itself. External tools are needed.
29
Onapsis Integrity Analyzer for SAP
30

Purpose: Detect modifications of ABAP code in an SAP system. Free download from http://www.onapsis.com/ianalizer (upcoming...) Proof-of-concept: Only working for SAP/Oracle 10g. Developed by Jordan Santarsieri and me @ the Onapsis Research Labs. Why you need it? Its not feasible to detect backdoors from inside the SAP system itself: Backdoors can leave the Programs Last modified date untouched. The analysis programs may have also been manipulated to hide the backdoors presence!

Want to do it manually? Number of SAP programs are measured in hundred of thousands (and even more). Onapsis Integrity Analyzer connects with the Database and performs snapshots of sensitive ABAP report tables. Periodically, new snapshots are compared with older snapshots and modified programs are identified. Tracking of SAP Notes is also considered. The detection of suspicious modifications should trigger a special investigation.
32
Live demo
33
Conclusions
34
Some Thoughts on SAP Backdoors

The Backdoor threat affects every information system; its not a specific SAP platform risk. Once an attacker obtained maximum privileges over an information system, it is really difficult to restrict his activities, and SAP is not the exception. SAP Backdoors can have devastating impacts over Business. These backdoors wont be installed for fun, its about MONEY.
The only sustainable choice the industry faces is the objective and responsible analysis of this threat.
35
Some Thoughts on SAP Backdoors

The best cost/effective protection: Minimize probability of the initial compromise. Automated controls. Periodic technical security assessments of SAP platforms. Vulnerability Assessments. Penetration Tests. Security Audits. Onapsiss Integrity Analyzer for SAP can help you to implement more in-depth reactive controls.
36
References
37
References
[1] http://www.onapsis.com/research/slides/ONAPSIS-Penetration_Testing_SAP.pdf [2] http://www.onapsis.com/resources/get.php?resid=ssid01
38
Questions?
[email protected]
39
Thank you!
www.onapsis.com
40

BlackHat EU 2010 Di Croce SAP Backdoors Slides

Uploaded by

Copyright:

Available Formats

BlackHat EU 2010 Di Croce SAP Backdoors Slides

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BlackHat EU 2010 Di Croce SAP Backdoors Slides

Uploaded by

Copyright:

Available Formats

SAP Backdoors

A ghost at the heart of your business

Mariano Nuez Di Croce

April 14, 2010

Black Hat Europe 2010 Briefings

SAP Backdoors Presentation

www.onapsis.com Onapsis S.R.L. 2010 All rights reserved

SAP Backdoors Presentation

www.onapsis.com Onapsis S.R.L. 2010 All rights reserved

SAP Backdoors Presentation

www.onapsis.com Onapsis S.R.L. 2010 All rights reserved

www.onapsis.com Onapsis S.R.L. 2010 All rights reserved

Why are SAP Backdoors special?

SoD is not enough to prevent Backdoors!

Ok, but which is the real risk?

ESPIONAGE SABOTAGE FRAUD

SAP Backdoors Presentation

www.onapsis.com Onapsis S.R.L. 2010 All rights reserved

The Initial Compromise

SAP Backdoors Presentation

www.onapsis.com Onapsis S.R.L. 2010 All rights reserved

Wide Attack Surface

SAP Backdoors Presentation

www.onapsis.com Onapsis S.R.L. 2010 All rights reserved

A Ghost in the User Master

SAP Backdoors Presentation

www.onapsis.com Onapsis S.R.L. 2010 All rights reserved

Welcome to the SAP world

SAP Backdoors Presentation

www.onapsis.com Onapsis S.R.L. 2010 All rights reserved

Oops! Downwards compatibility

Oops! Downwards compatibility

Parameter can be modified dynamically! (No SAP restart required)

SAP Backdoors Presentation

www.onapsis.com Onapsis S.R.L. 2010 All rights reserved

SAP Backdoors Presentation

www.onapsis.com Onapsis S.R.L. 2010 All rights reserved

Backdoors in SAP Business Modules

SAP Backdoors Presentation

www.onapsis.com Onapsis S.R.L. 2010 All rights reserved

Welcome (back) to the SAP World

The Change and Transport System

Unauthorized modification of ABAP Programs directly in the Production System is possible.

SAPs Heart: The Database

SAP Backdoors Presentation

www.onapsis.com Onapsis S.R.L. 2010 All rights reserved

Backdoors in the Authentication Procedure

SAP Backdoors Presentation

www.onapsis.com Onapsis S.R.L. 2010 All rights reserved

Protection for Critical ABAP Programs

SAPMSYST The SAPs Cop

SAP Backdoors Presentation

www.onapsis.com Onapsis S.R.L. 2010 All rights reserved

SAP Backdoors Presentation

www.onapsis.com Onapsis S.R.L. 2010 All rights reserved

SAP Backdoors Presentation

www.onapsis.com Onapsis S.R.L. 2010 All rights reserved

Onapsis Integrity Analyzer for SAP

SAP Backdoors Presentation

www.onapsis.com Onapsis S.R.L. 2010 All rights reserved