CVE Vulnerabilities

CVE-2021-1737

Out-of-bounds Write

Published: Apr 02, 2021 | Modified: Jun 03, 2022
CVSS 3.x
7.8
HIGH
Source:
NVD
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
CVSS 2.x
6.8 MEDIUM
AV:N/AC:M/Au:N/C:P/I:P/A:P
RedHat/V2
RedHat/V3
Ubuntu

An out-of-bounds write was addressed with improved input validation. This issue is fixed in macOS Big Sur 11.2, Security Update 2021-001 Catalina, Security Update 2021-001 Mojave. Processing a maliciously crafted image may lead to arbitrary code execution.

Weakness

The software writes 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 *
Mac_os_x Apple 10.14 *
Mac_os_x Apple 10.14.6 10.14.6
Mac_os_x Apple 10.14.6 10.14.6
Mac_os_x Apple 10.14.6 10.14.6
Mac_os_x Apple 10.14.6 10.14.6
Mac_os_x Apple 10.14.6 10.14.6
Mac_os_x Apple 10.14.6 10.14.6
Mac_os_x Apple 10.14.6 10.14.6
Mac_os_x Apple 10.14.6 10.14.6
Ipados Apple * *
Iphone_os Apple * *
Mac_os_x Apple 10.14.6 10.14.6
Mac_os_x Apple 10.14.6 10.14.6
Mac_os_x Apple 10.14.6 10.14.6
Mac_os_x Apple 10.14.6 10.14.6
Mac_os_x Apple 10.14.6 10.14.6
Mac_os_x Apple 10.14.6 10.14.6
Mac_os_x Apple 10.15.7 10.15.7
Mac_os_x Apple 10.15.7 10.15.7
Mac_os_x Apple 10.15.7 10.15.7
Macos Apple 11.0 *

Potential Mitigations

  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.

  • For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer.

  • Be wary that a language’s interface to native code may still be subject to overflows, even if the language itself is theoretically safe.

  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.

  • Examples include the Safe C String Library (SafeStr) by Messier and Viega [REF-57], and the Strsafe.h library from Microsoft [REF-56]. These libraries provide safer versions of overflow-prone string-handling functions.

  • Run or compile the software using features or extensions that automatically provide a protection mechanism that mitigates or eliminates buffer overflows.

  • For example, certain compilers and extensions provide automatic buffer overflow detection mechanisms that are built into the compiled code. Examples include the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice.

  • Consider adhering to the following rules when allocating and managing an application’s memory:

  • Run or compile the software using features or extensions that randomly arrange the positions of a program’s executable and libraries in memory. Because this makes the addresses unpredictable, it can prevent an attacker from reliably jumping to exploitable code.

  • Examples include Address Space Layout Randomization (ASLR) [REF-58] [REF-60] and Position-Independent Executables (PIE) [REF-64].

References