CVE Vulnerabilities

CVE-2023-28204

Out-of-bounds Read

Published: Jun 23, 2023 | Modified: Jan 05, 2024
CVSS 3.x
6.5
MEDIUM
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
CVSS 2.x
RedHat/V2
RedHat/V3
6.5 MODERATE
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Ubuntu
MEDIUM

An out-of-bounds read was addressed with improved input validation. This issue is fixed in watchOS 9.5, tvOS 16.5, macOS Ventura 13.4, iOS 15.7.6 and iPadOS 15.7.6, Safari 16.5, iOS 16.5 and iPadOS 16.5. Processing web content may disclose sensitive information. Apple is aware of a report that this issue may have been actively exploited.

Weakness

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

Affected Software

Name Vendor Start Version End Version
Safari Apple * 16.5 (excluding)
Ipados Apple * 15.7.6 (excluding)
Ipados Apple 16.0 (including) 16.5 (excluding)
Iphone_os Apple * 15.7.6 (excluding)
Iphone_os Apple 16.0 (including) 16.5 (excluding)
Macos Apple 13.0 (including) 13.4 (excluding)
Tvos Apple * 16.5 (excluding)
Watchos Apple * 9.5 (excluding)
Red Hat Enterprise Linux 8 RedHat webkit2gtk3-0:2.38.5-1.el8_8.4 *
Red Hat Enterprise Linux 9 RedHat webkit2gtk3-0:2.38.5-1.el9_2.2 *
Qtwebkit-opensource-src Ubuntu bionic *
Qtwebkit-opensource-src Ubuntu kinetic *
Qtwebkit-opensource-src Ubuntu lunar *
Qtwebkit-opensource-src Ubuntu trusty *
Qtwebkit-opensource-src Ubuntu xenial *
Qtwebkit-source Ubuntu bionic *
Qtwebkit-source Ubuntu trusty *
Qtwebkit-source Ubuntu xenial *
Webkit2gtk Ubuntu bionic *
Webkit2gtk Ubuntu focal *
Webkit2gtk Ubuntu jammy *
Webkit2gtk Ubuntu kinetic *
Webkit2gtk Ubuntu lunar *
Webkit2gtk Ubuntu upstream *
Webkit2gtk Ubuntu xenial *
Webkitgtk Ubuntu bionic *
Webkitgtk Ubuntu trusty *
Webkitgtk Ubuntu xenial *
Wpewebkit Ubuntu trusty *

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.

References