Advisory

A note with CVSS 4.3 for component FIN-FSCM-TRM-TM-TR was released by SAP on 12.11.2019. The correction/advisory 2819170 was described with "[CVE-2019-0383] Missing Authorization check in SAP Treasury and Risk Management (Transaction Management)" and affects the system type ABAP.

A workaround does not exist, according to SAP Security Advisory team. It is advisable to implement the correction as monthly patch process.

The vulnerability addressed is missing authorization check within ABAP.

Missing authority checks are still the most common security defect related to authorizations in custom code. Since SAP uses an explicit authorization model, an authority checks must be coded in order to be executed. If an explicit check is not coded, all users have access. This type of vulnerability not only exists in SAP standard it also exists in customer coding. Check your custom developments for vulnerabilities that pose a risk to your systems. SecurityBridge helps detect code vulnerabilities before they are implemented in production.

Risk specification

Transaction Management in SAP Treasury and Risk Management does not perform necessary authorization checks for an authenticated user, resulting in escalation of privileges

Solution

Additional authorization checks are added before displaying the data for relevant transaction codes (authorization objects 'T_DEAL_PD', 'T_DEAL_PF', 'T_DEAL_AG', 'T_DEAL_DP').

Affected System

The advisory 2819170 describes a problem within an ABAP based systems of a specific version. Affected versions are described below. ABAP software is deployed in various software components and is widely used within the SAP product portfolio.

SAP NetWeaver Application Server (formally known as SAP Web Application Server) is a building block of SAP NetWeaver. It is the foundation for most software products developed by SAP SE. SAP NetWeaver systems exist with Java and/or ABAP stacks. The advisory could be relevant for single and dual-stack ABAP installations.

The advisory is valid for

Releated advisories

Disclaimer

SecurityBridge takes the security of SAP products very seriously. We very much encourage the responsible disclosure of security vulnerabilities. If you have detected a vulnerability concerning 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 SecurityBridge advisory are generated and continuously enriched by our Team at SecurityBridge and affiliated security consultants, partners, customers of the SecurityBridge Platform, SAP support, and advisory groups.

We do not disclose zero-day vulnerabilities unless a security patch has been made available to the public. 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, SecurityBridge only discloses issues where the fixing security note has been released. 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.

SecurityBridge - Code vulnerabilty analysis

Secure code
Customer created code contains security risks. Use modern technologies to detect coding flaws mitigate unneccessary risks. Start to detect:

Open & Native SQL Injection
Potential backdoors
Insuffient authorization checks of user administration bypassed
Injections of operating system commands
and many more..

Start scanning for ABAP Code vulnerabilities

Follow @_securitybridge

Notifications

Affected system ABAP

CVSS 4.3

Component FIN-FSCM-TRM-TM-TR

Patch Day2019-11

Released on2019/11/12

SAP Note 2819170

Workaround No

Advisory

Risk specification

Solution

Affected System

Disclaimer

_{Affected system}
ABAP

_CVSS
4.3

_Component
FIN-FSCM-TRM-TM-TR

_{Patch Day}
2019-11

_{Released
on}
2019/11/12

_{SAP Note}
2819170

_Workaround
No