CVE-2024-44215VulnerabilityPublished 28 Oct 2024Updated 2 Apr 2026

CVE-2024-44215: Apple iOS and iPadOS · Processing an image may result in disclosure of process memory

Affects Apple iOS and iPadOSSource CVE Database V5

Not known to be exploited · CVSS 5.5 Medium · fixed in 17.7.1 : update Apple iOS and iPadOS when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

5.5Medium

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 17.7.1

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

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: None
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: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
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: None: There is no loss of integrity within 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 28 Oct 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 2026-10-25.

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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC 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.

What to do

Affected software

Product	Affected	Fixed in
Apple iOS and iPadOS	Affected =0	Fixed in–

AI-suggested

To mitigate CVE-2024-44215, organizations and users should promptly update affected Apple devices to the latest patched versions: iOS 17.7.1, iPadOS 17.7.1, macOS Sequoia 15.1, macOS Sonoma 14.7.1, macOS Ventura 13.7.1, tvOS 18.1, visionOS 2.1, and watchOS 11.1. Beyond patching, organizations should implement strict controls on the sources of images processed on corporate devices, including filtering or blocking images from untrusted or unknown origins. User awareness training should emphasize the risks of opening unsolicited or suspicious images, especially from unknown senders. Deploying mobile device management (MDM) solutions can help enforce update policies and restrict risky app behaviors. Network-level protections such as content scanning and sandboxing of media files before delivery to end devices can reduce exposure. Monitoring for unusual application behavior or memory access patterns on Apple devices may help detect exploitation attempts. Finally, organizations should maintain an inventory of Apple devices and ensure compliance with security baselines that include timely OS updates.

Description

This issue was addressed with improved checks. This issue is fixed in iOS 17.7.1 and iPadOS 17.7.1, iOS 18.1 and iPadOS 18.1, macOS Sequoia 15.1, macOS Sonoma 14.7.1, macOS Ventura 13.7.1, tvOS 18.1, visionOS 2.1, watchOS 11.1. Processing an image may result in disclosure of process memory.

Impact

The primary impact of CVE-2024-44215 is the potential unauthorized disclosure of sensitive process memory on Apple mobile devices. This can lead to leakage of confidential information such as authentication tokens, encryption keys, or personal user data, which could be leveraged for further attacks or privacy violations. Although the vulnerability does not allow code execution or system compromise directly, the information disclosure can weaken overall device security posture. Organizations relying on Apple iOS and iPadOS devices for sensitive communications or operations may face increased risk of data leakage if devices remain unpatched. The requirement for user interaction limits the ease of exploitation but does not eliminate risk, especially in environments where users may be targeted with malicious images via email, messaging apps, or web browsing. The vulnerability affects a broad range of Apple operating systems, increasing the scope of potentially impacted devices globally. However, the absence of known exploits in the wild suggests that immediate widespread impact is limited but could change if exploit code is developed.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 2 Apr 2026, 23:57 UTC

Technical details

References

Community reviews

Related threats