CVE Vulnerabilities


Out-of-bounds Read

Published: Jun 09, 2021 | Modified: Oct 31, 2022
CVSS 3.x
CVSS 2.x

SAP NetWeaver AS for ABAP (RFC Gateway), versions - KRNL32NUC - 7.22,7.22EXT, KRNL64NUC - 7.22,7.22EXT,7.49, KRNL64UC - 8.04,7.22,7.22EXT,7.49,7.53,7.73, KERNEL - 7.22,8.04,7.49,7.53,7.73,7.77,7.81,7.82,7.83, allows an unauthenticated attacker without specific knowledge of the system to send a specially crafted packet over a network which will trigger an internal error in the system due to improper input validation in method memmove() causing the system to crash and rendering it unavailable. In this attack, no data in the system can be viewed or modified.


The product reads data past the end, or before the beginning, of the intended buffer.

Affected Software

Name Vendor Start Version End Version
Netweaver_abap Sap kernel_7.22 (including) kernel_7.22 (including)
Netweaver_abap Sap kernel_7.49 (including) kernel_7.49 (including)
Netweaver_abap Sap kernel_7.53 (including) kernel_7.53 (including)
Netweaver_abap Sap kernel_7.73 (including) kernel_7.73 (including)
Netweaver_abap Sap kernel_8.04 (including) kernel_8.04 (including)
Netweaver_abap Sap krnl32nuc_7.22 (including) krnl32nuc_7.22 (including)
Netweaver_abap Sap krnl32nuc_7.22ext (including) krnl32nuc_7.22ext (including)
Netweaver_abap Sap krnl64nuc_7.22 (including) krnl64nuc_7.22 (including)
Netweaver_abap Sap krnl64nuc_7.22ext (including) krnl64nuc_7.22ext (including)
Netweaver_abap Sap krnl64nuc_7.49 (including) krnl64nuc_7.49 (including)
Netweaver_abap Sap krnl64uc_7.22 (including) krnl64uc_7.22 (including)
Netweaver_abap Sap krnl64uc_7.22ext (including) krnl64uc_7.22ext (including)
Netweaver_abap Sap krnl64uc_7.49 (including) krnl64uc_7.49 (including)
Netweaver_abap Sap krnl64uc_7.53 (including) krnl64uc_7.53 (including)
Netweaver_abap Sap krnl64uc_7.73 (including) krnl64uc_7.73 (including)
Netweaver_abap Sap krnl64uc_8.04 (including) krnl64uc_8.04 (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.
  • To reduce the likelihood of introducing an out-of-bounds read, ensure that you validate and ensure correct calculations for any length argument, buffer size calculation, or offset. Be especially careful of relying on a sentinel (i.e. special character such as NUL) in untrusted inputs.