A function module of SAP NetWeaver AS ABAP (Reconciliation Framework), versions - 700, 701, 702, 710, 711, 730, 731, 740, 750, 751, 752, 75A, 75B, 75B, 75C, 75D, 75E, 75F, allows a high privileged attacker to inject code that can be executed by the application. An attacker could thereby delete some critical information and could make the SAP system completely unavailable.
Weakness
The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes code syntax before using the input in a dynamic evaluation call (e.g. “eval”).
Affected Software
| Name |
Vendor |
Start Version |
End Version |
| Netweaver_application_server_abap |
Sap |
75a (including) |
75a (including) |
| Netweaver_application_server_abap |
Sap |
75b (including) |
75b (including) |
| Netweaver_application_server_abap |
Sap |
75c (including) |
75c (including) |
| Netweaver_application_server_abap |
Sap |
75d (including) |
75d (including) |
| Netweaver_application_server_abap |
Sap |
75e (including) |
75e (including) |
| Netweaver_application_server_abap |
Sap |
75f (including) |
75f (including) |
| Netweaver_application_server_abap |
Sap |
700 (including) |
700 (including) |
| Netweaver_application_server_abap |
Sap |
701 (including) |
701 (including) |
| Netweaver_application_server_abap |
Sap |
702 (including) |
702 (including) |
| Netweaver_application_server_abap |
Sap |
710 (including) |
710 (including) |
| Netweaver_application_server_abap |
Sap |
711 (including) |
711 (including) |
| Netweaver_application_server_abap |
Sap |
730 (including) |
730 (including) |
| Netweaver_application_server_abap |
Sap |
731 (including) |
731 (including) |
| Netweaver_application_server_abap |
Sap |
740 (including) |
740 (including) |
| Netweaver_application_server_abap |
Sap |
750 (including) |
750 (including) |
| Netweaver_application_server_abap |
Sap |
751 (including) |
751 (including) |
| Netweaver_application_server_abap |
Sap |
752 (including) |
752 (including) |
Potential Mitigations
- Assume all input is malicious. Use an “accept known good” input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
- When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, “boat” may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as “red” or “blue.”
- Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code’s environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
- Inputs should be decoded and canonicalized to the application’s current internal representation before being validated (CWE-180, CWE-181). Make sure that your application does not inadvertently decode the same input twice (CWE-174). Such errors could be used to bypass allowlist schemes by introducing dangerous inputs after they have been checked. Use libraries such as the OWASP ESAPI Canonicalization control.
- Consider performing repeated canonicalization until your input does not change any more. This will avoid double-decoding and similar scenarios, but it might inadvertently modify inputs that are allowed to contain properly-encoded dangerous content.
References