On 20.09.2021 a security relevant correction has been released by SAP SE. The manufacturer resolves an issue within ABAP.
SAP Note 3089438 addresses "Missing transaction start (AU3) entries in the Security Audit Log" to prevent missing logging functionality with a hot news risk for exploitation.
A workaround does not exist, according to SAP Security Advisory team. It is advisable to implement the correction as monthly patch process, the team suggests.
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 specificationSpecific transaction calls are not recorded within audit class AU3 in the SAP Security Audit Log
Deduplication introduced via 2938831 leads to not recording transaction calls in certain situations.
The advisory 3089438 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
- SAP_BASIS 700 - 702
- SAP_BASIS 731
- SAP_BASIS 740 64
- SAP_BASIS 750 - 756