SAP NetWeaver Application Server ABAP allows an unauthenticated attacker to craft a URL link that could bypass allowlist controls. Depending on the web applications provided by this server, the attacker might inject CSS code or links into the web application that could allow the attacker to read or modify information. There is no impact on availability of application.
Weakness
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Netweaver_application_server_abap | Sap | 755 (including) | 755 (including) |
| Netweaver_application_server_abap | Sap | 756 (including) | 756 (including) |
| Netweaver_application_server_abap | Sap | 757 (including) | 757 (including) |
| Netweaver_application_server_abap | Sap | 758 (including) | 758 (including) |
| Netweaver_application_server_abap | Sap | sap_basis_700 (including) | sap_basis_700 (including) |
| Netweaver_application_server_abap | Sap | sap_basis_701 (including) | sap_basis_701 (including) |
| Netweaver_application_server_abap | Sap | sap_basis_702 (including) | sap_basis_702 (including) |
| Netweaver_application_server_abap | Sap | sap_basis_731 (including) | sap_basis_731 (including) |
| Netweaver_application_server_abap | Sap | sap_basis_912 (including) | sap_basis_912 (including) |
| Netweaver_application_server_abap | Sap | sap_ui_754 (including) | sap_ui_754 (including) |
Extended Description
Access control involves the use of several protection mechanisms such as:
When any mechanism is not applied or otherwise fails, attackers can compromise the security of the product by gaining privileges, reading sensitive information, executing commands, evading detection, etc. There are two distinct behaviors that can introduce access control weaknesses:
Potential Mitigations
- Compartmentalize the system to have “safe” areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
- Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
Related Attack Patterns
- https://cwe.mitre.org/data/definitions/19.html
- https://cwe.mitre.org/data/definitions/441.html
- https://cwe.mitre.org/data/definitions/478.html
- https://cwe.mitre.org/data/definitions/479.html
- https://cwe.mitre.org/data/definitions/502.html
- https://cwe.mitre.org/data/definitions/503.html
- https://cwe.mitre.org/data/definitions/536.html
- https://cwe.mitre.org/data/definitions/546.html
- https://cwe.mitre.org/data/definitions/550.html
- https://cwe.mitre.org/data/definitions/551.html
- https://cwe.mitre.org/data/definitions/552.html
- https://cwe.mitre.org/data/definitions/556.html
- https://cwe.mitre.org/data/definitions/558.html
- https://cwe.mitre.org/data/definitions/562.html
- https://cwe.mitre.org/data/definitions/563.html
- https://cwe.mitre.org/data/definitions/564.html
- https://cwe.mitre.org/data/definitions/578.html