Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Vulnerabilities / Threats

11/9/2015
02:15 PM
Connect Directly
Twitter
RSS
E-Mail
50%
50%

6 Critical SAP HANA Vulns Can't Be Fixed With Patches

Onapsis releases 21 SAP HANA security advisories, including some Trexnet vulnerabilities that require upgrades and reconfigurations.

Researchers at Onapsis today released an unprecedented 21 security advisories for all SAP HANA-based applications, including eight critical vulnerabilities, six of which cannot be fixed by simple patches.

Collectively, the critical vulnerabilities can be exploited remotely and enable attackers to execute code, move files, delete data, completely compromise the system, access and manage business-relevant data and processes, and render all SAP systems unavailable.

SAP HANA is the in-memory processing technology that powers some of the biggest big-data analytics projects, as well as SAP's other business products, including customer relationship management (CRM), enterprise resource planning (ERP), and product lifecycle management (PLM) systems.

Onapsis CTO Juan Pablo Perez-Etchegoyen says most enterprises are "not just running one SAP product. Typically, they're running the whole suite. ... What happens if one of these systems goes down, when you have so many processes going to this system?"

The impact of an SAP outage or compromise will vary by company and by what SAP applications they use, says Etchegoyen, but one Onapsis customer told him last year that a SAP outage could cost its company $22 million per minute.

Six of the critical vulnerabilities of gravest concern are due to a configuration problem, and therefore cannot be fixed just by patching, he says. They affect the TREXnet protocol, used by the HANA Database's TREX servers -- NameServer, Preprocessor, IndexServer, StatisticsServer, WebDispatcher, XSEngine, or CompileServer -- to communicate with one another. If the TREXnet communication is not secured with authentication, attackers can exploit a variety of vulnerabilities by sending specially crafted packets to these TREX server ports. Those vulnerabilities are:

  • Trexnet remote file write -- override relevant info and render system unavailable due to corrupted data
  • Trexnet remote directory deletion -- delete info and render system unavailable
  • Trexnet remote file deletion -- delete data, affect integrity, and potentially render system unavailable
  • Trexnet file move -- relocate info stored in system so it's easy to access; it could also potentially render the system unavailable due to a non-integral file system
  • Trexnet remote command execution -- completely compromise the system and would be able to access and manage any business-relevant information or processes, execute commands with admin privileges
  • Trexnet remote Python execution -- completely compromise the system and would be able to access and manage any business-relevant information or processes; executing arbitrary Python modules in SAP HANA with admin privileges

To close those holes, users need to upgrade to the latest version of the software and reconfigure their settings to enable strong authentication and encryption measures on TREXnet.

There are another two critical vulnerabilities in the HANA Database due to incorrect calculation of buffer size:

  • HTTP remote code execution. By sending specially crafted HTTP packets to SAP HANA XSServer, a remote, unauthenticated attacker could completely compromise the system, access and manage business-relevant information and processes. This could be achieved remotely and potentially through the Internet, affecting on-premise and cloud-based HANA solutions.
  • SQL remote code execution. By sending specially crafted packets to SQL interfaces, attackers could compromise the platform, executing arbitrary code or performing a denial of service attack, completely compromise system, access and manage business-relevant information and processes.

In addition to the critical ones, Onapsis' release also contains six high-severity and seven medium-severity vulnerabilities.

Exacerbating the problem is the fact that while many of businesses' core processes run on SAP systems, information security teams have very little visibility into these systems and how they're secured, according to Etchegoyen. 

"We still have these two teams separated," says Etchegoyen. "That's something we're trying to evangelize. They need to have more communication between those two teams."

Sara Peters is Senior Editor at Dark Reading and formerly the editor-in-chief of Enterprise Efficiency. Prior that she was senior editor for the Computer Security Institute, writing and speaking about virtualization, identity management, cybersecurity law, and a myriad ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
SanjayK204
50%
50%
SanjayK204,
User Rank: Apprentice
5/31/2018 | 2:32:44 AM
appreciate
H,

 

Thanks for the tip, appreciate it. Your article definitely helped me to understand the core concepts.
I'm most excited about the details your article touch based! I assume it doesn't come out of the box, it sounds like you are saying we'd need to write in the handlers ourselves.
Is there any other articles you would recommend to understand this better?

 

In the HANA migration guide, it is stated to run some consistency checks in FICO (see verbiage below).

I have run these, but I really don't know what I'm looking for - are we running just to make sure they run, running to validate numbers on the reports? Thoughts & guidance are appreciated. Thank you!

3.8 FI/CO: Performing Additional Consistency Checks

To ensure that the source system is consistent, user of Financial Accounting (FI) and Controlling (CO) need to perform some preparatory activities, among others additional consistency checks.

3.2 Product-Specific Preparations of the System Copy Guide, which is mentioned in Further Documentation [page 6].Caution Make sure that no customer data is changed in the meantime. Proceed as follows:

Procedure

1. FI: Run job SAPF190 to perform an additional consistency check. Choose AccountingFinancial AccountingGeneral ledgerPeriodic ProcessingClosingCheck/count. Then choose for○ classic FI: Reconciliation○ new general ledger: Reconciliation (New)

2. FI: You can further check consistency by running the jobs listed below:

○ RFUMSV00 (tax on sales/purchases)

○ RAGITT01 (asset history sheet)

○ RAZUGA01 (asset acquisitions)

○ RAABGA01 (fixed asset retirements)

3. CO: Run the report group 1SIP

 




Appreciate your effort for making such useful blogs and helping the community.  

 

Thanks a heaps,

Irene Hynes

 
News
Former CISA Director Chris Krebs Discusses Risk Management & Threat Intel
Kelly Sheridan, Staff Editor, Dark Reading,  2/23/2021
Edge-DRsplash-10-edge-articles
Security + Fraud Protection: Your One-Two Punch Against Cyberattacks
Joshua Goldfarb, Director of Product Management at F5,  2/23/2021
News
Cybercrime Groups More Prolific, Focus on Healthcare in 2020
Robert Lemos, Contributing Writer,  2/22/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Building the SOC of the Future
Building the SOC of the Future
Digital transformation, cloud-focused attacks, and a worldwide pandemic. The past year has changed the way business works and the way security teams operate. There is no going back.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-26200
PUBLISHED: 2021-02-26
A component of Kaspersky custom boot loader allowed loading of untrusted UEFI modules due to insufficient check of their authenticity. This component is incorporated in Kaspersky Rescue Disk (KRD) and was trusted by the Authentication Agent of Full Disk Encryption in Kaspersky Endpoint Security (KES...
CVE-2019-18942
PUBLISHED: 2021-02-26
Micro Focus Solutions Business Manager versions prior to 11.7.1 are vulnerable to stored XSS. The application reflects previously stored user input without encoding.
CVE-2019-18943
PUBLISHED: 2021-02-26
Micro Focus Solutions Business Manager versions prior to 11.7.1 are vulnerable to XML External Entity Processing (XXE) on certain operations.
CVE-2019-18944
PUBLISHED: 2021-02-26
Micro Focus Solutions Business Manager Application Repository versions prior to 11.7.1 are vulnerable to reflected XSS.
CVE-2019-18945
PUBLISHED: 2021-02-26
Micro Focus Solutions Business Manager Application Repository versions prior to 11.7.1 are vulnerable to privilege escalation vulnerability.