Advisory

A note with CVSS 4.2 for component HAN-DB-SEC was released by SAP on 08.12.2020. The correction/advisory 2978768 was described with "[CVE-2020-26834 ] Improper authentication in SAP HANA database" and affects the system type HANA Platform.

A workaround exists, according to SAP Security Advisory team. It is advisable to implement the correction as part of maintenance.

The vulnerability addressed is missing authentication check within HANA Platform.

Risk specification

The SAP HANA database does not correctly validate the user name when performing SAML bearer token-based user authentication, allowing to manipulate a valid existing SAML bearer token to authenticate as a user whose name is identical to the truncated user name for whom the SAML bearer token was issued.

Solution

The SAP HANA database now properly performs the validation of the SAML token during the authentication.  Although an alternative solution exists, it is advisable to apply the correction! This is the workaround, which was suggested by the SAP security experts: "Disable the SAML authentication only for the affected users.".

Affected System

SAP HANA is a high-performance in-memory database and the basis for a so called "Real-Time Data Platform". SAP HANA allows online transaction processing (OLTP) and online analytical processing (OLAP) on one system. SAP HANA Extended Application Services (aka SAP HANA XS) is a key aspect of SAP HANA as a platform.

Additonal resources

The advisory is valid for

  • HDB 1.00
  • HDB 2.00

 

Disclaimer

ABEX takes the security of SAP products very seriously. We very much encourage the responsible disclosure of security vulnerabilities. If you have detected a vulnerability in one of the SAP software products – either in the latest or in a former product version follow the guidelines and processes in accordance with the SAP portal page “Report a Security Vulnerability to SAP”.

The advisories found within the ABEX security advisory are generated and continuously enriched by ABEX and affiliated security consultants, partners, customers of the SecurityBridge security suite, SAP support, and advisory groups.

There is no disclosure of zero-day vulnerabilities. In such case, the platform only provides details on which version or signature updates are available within the SecurityBridge platform in order to monitor or measure the vulnerability

In accordance with SAP guidelines, ABEX only discloses issues where the fixing security note has been released at least three months ago. The vulnerability platform makes no references to available exploits or Proof of Concepts (PoC). Advisories and vulnerabilities will always mention the fixing security note or hints to the corresponding SAP documentation.

 

Follow us:

 

SecurityBridge

SecurityBridgefor SAP©
empowers security teams with forward-looking, high fidelity, adversary-focused intelligence and actionable events from SAP Netweaver based systems.