VYPR
Unrated severityNVD Advisory· Published May 8, 2023· Updated Aug 2, 2024

CVE-2023-23528

CVE-2023-23528

Description

An out-of-bounds read in Apple's Bluetooth stack allows disclosure of process memory via a maliciously crafted Bluetooth packet; fixed in iOS 16.4, iPadOS 16.4, and tvOS 16.4.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

An out-of-bounds read in Apple's Bluetooth stack allows disclosure of process memory via a maliciously crafted Bluetooth packet; fixed in iOS 16.4, iPadOS 16.4, and tvOS 16.4.

Vulnerability

An out-of-bounds read vulnerability exists in the Bluetooth stack of Apple iOS, iPadOS, and tvOS. The issue is present in versions prior to iOS 16.4, iPadOS 16.4, and tvOS 16.4. Processing a maliciously crafted Bluetooth packet can trigger an out-of-bounds read, leading to disclosure of process memory. [1][2]

Exploitation

An attacker in close proximity to a vulnerable device could send a specially crafted Bluetooth packet. No authentication or user interaction is required beyond the device having Bluetooth enabled and being in range. The attacker would need to be within Bluetooth range (typically up to 10 meters) and send the malicious packet to trigger the out-of-bounds read.

Impact

Successful exploitation results in disclosure of process memory, potentially exposing sensitive information such as cryptographic keys, passwords, or other data resident in the kernel or application memory. The impact is limited to information disclosure; no code execution is indicated.

Mitigation

Apple has addressed the issue in iOS 16.4, iPadOS 16.4, and tvOS 16.4, released on March 27, 2023. Users should update their devices to the latest available versions. No workarounds are available; the only mitigation is to apply the security update. [1][2]

AI Insight generated on May 27, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

5

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

2

News mentions

0

No linked articles in our index yet.