CVE Vulnerabilities


Out-of-bounds Read

Published: May 26, 2022 | Modified: Jun 08, 2022
CVSS 3.x
CVSS 2.x

An out-of-bounds read issue was addressed with improved input validation. This issue is fixed in Security Update 2022-004 Catalina, macOS Monterey 12.4, macOS Big Sur 11.6.6. Processing a maliciously crafted AppleScript binary may result in unexpected application termination or disclosure of process memory.


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

Affected Software

Name Vendor Start Version End Version
Mac_os_x Apple 10.15 (excluding) 10.15.7 (excluding)
Mac_os_x Apple 10.15.7 (including) 10.15.7 (including)
Mac_os_x Apple 10.15.7-security_update_2020 (including) 10.15.7-security_update_2020 (including)
Mac_os_x Apple 10.15.7-security_update_2020-001 (including) 10.15.7-security_update_2020-001 (including)
Mac_os_x Apple 10.15.7-security_update_2020-005 (including) 10.15.7-security_update_2020-005 (including)
Mac_os_x Apple 10.15.7-security_update_2020-007 (including) 10.15.7-security_update_2020-007 (including)
Mac_os_x Apple 10.15.7-security_update_2021-001 (including) 10.15.7-security_update_2021-001 (including)
Mac_os_x Apple 10.15.7-security_update_2021-002 (including) 10.15.7-security_update_2021-002 (including)
Mac_os_x Apple 10.15.7-security_update_2021-003 (including) 10.15.7-security_update_2021-003 (including)
Mac_os_x Apple 10.15.7-security_update_2021-006 (including) 10.15.7-security_update_2021-006 (including)
Mac_os_x Apple 10.15.7-security_update_2021-007 (including) 10.15.7-security_update_2021-007 (including)
Mac_os_x Apple 10.15.7-security_update_2021-008 (including) 10.15.7-security_update_2021-008 (including)
Mac_os_x Apple 10.15.7-security_update_2022-001 (including) 10.15.7-security_update_2022-001 (including)
Mac_os_x Apple 10.15.7-security_update_2022-002 (including) 10.15.7-security_update_2022-002 (including)
Mac_os_x Apple 10.15.7-security_update_2022-003 (including) 10.15.7-security_update_2022-003 (including)
Mac_os_x Apple 10.15.7-supplemental_update (including) 10.15.7-supplemental_update (including)
Macos Apple 11.0 (including) 11.6.6 (excluding)
Macos Apple 12.0.0 (including) 12.4 (excluding)

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.