VulnerabilityPublished 12 Dec 2024Updated 4 Nov 2025

CVE-2024-54514: The issue was addressed with improved checks

Source GCVE Database

Compare

Authoritative record:CVE-2024-54514· High 8.2

Not known to be exploited · CVSS 8.2 High.

Data as of 30 Oct 2026, 15:58 UTC

CVSS 3.1 base score

8.2High

How severe the flaw is on the 0–10 CVSS scale.

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Changed
Confidentiality: High
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 11 Dec 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-wm24-225r-44gm

What to do

AI-suggested

Apply the official patches provided by Apple by upgrading to watchOS 11.2, tvOS 18.2, macOS Sequoia 15.2, iOS 18.2, iPadOS 18.2, macOS Ventura 13.7.2, or macOS Sonoma 14.7.2. These versions include improved checks that address the vulnerability. No other mitigation steps are indicated.

Description

CVE-2024-54514 is a high-severity vulnerability affecting multiple Apple operating systems including watchOS, tvOS, macOS, iOS, and iPadOS. The flaw could allow an application to escape its sandbox, potentially leading to unauthorized access to system resources or data. The issue has been addressed by Apple through improved checks and is fixed in specific versions of these operating systems.

Impact

An application exploiting this vulnerability could escape its sandbox, potentially gaining unauthorized access to system resources or sensitive data, compromising confidentiality and integrity of the affected system. This could lead to significant security breaches if exploited.

Summary

CVE-2024-54514 is a vulnerability that allows an app to potentially break out of its sandbox environment on Apple devices. This sandbox escape could lead to elevated privileges or unauthorized access beyond the app's intended boundaries. Apple has fixed this issue by implementing improved checks in watchOS 11.2, tvOS 18.2, macOS Sequoia 15.2, iOS 18.2, iPadOS 18.2, macOS Ventura 13.7.2, and macOS Sonoma 14.7.2. The CVSS v3.1 score is 8.2, indicating high severity, with attack vector local, low attack complexity, no privileges required, user interaction required, scope changed, and high impact on confidentiality and integrity but no impact on availability.

References

Community reviews

Loading reviews…