CVE-2023-42872VulnerabilityPublished 10 Jan 2024Updated 4 Nov 2025

CVE-2023-42872: Apple iOS and iPadOS · An app may be able to access sensitive user data

Affects Apple iOS and iPadOSSource CVE Database V5

Not known to be exploited · CVSS 5.5 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

5.5Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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 10 Jan 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-26.

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

AI-suggested

1. Promptly update all Apple devices to iOS 17, iPadOS 17, or macOS Sonoma 14 to apply the security patches that address this vulnerability. 2. Enforce strict mobile device management (MDM) policies to control app installations, allowing only apps from trusted sources such as the Apple App Store and blocking sideloading or enterprise apps unless verified. 3. Educate users about the risks of installing untrusted applications and the importance of applying OS updates promptly. 4. Implement endpoint security solutions that can detect and block suspicious app behaviors or unauthorized data access attempts on iOS and iPadOS devices. 5. Regularly audit device compliance and patch status across the organization to ensure no vulnerable devices remain in use. 6. For high-risk environments, consider restricting sensitive data access on mobile devices or using containerization and data loss prevention (DLP) tools to limit exposure. 7. Monitor for unusual data access patterns or app permissions that could indicate exploitation attempts. 8. Coordinate with Apple support and security advisories to stay informed about any emerging threats or additional mitigations related to this vulnerability.

Description

The issue was addressed with additional permissions checks. This issue is fixed in macOS Sonoma 14, iOS 17 and iPadOS 17. An app may be able to access sensitive user data.

Impact

For European organizations, this vulnerability could lead to unauthorized disclosure of sensitive user or corporate data on iOS and iPadOS devices, potentially compromising personal information, intellectual property, or confidential communications. Given the widespread use of Apple devices in European enterprises and among consumers, especially in sectors like finance, healthcare, and government, the risk of data leakage could have regulatory and reputational consequences. The vulnerability does not affect data integrity or availability, so it is less likely to cause system disruptions or data manipulation. However, the confidentiality breach could facilitate further attacks such as social engineering or targeted phishing. The requirement for local access and user interaction somewhat limits remote exploitation but does not eliminate risk, particularly in environments where device control is less stringent or where users may be tricked into installing malicious apps. Organizations with bring-your-own-device (BYOD) policies or mobile workforces are especially vulnerable if devices are not promptly updated. Compliance with GDPR and other data protection laws in Europe increases the importance of mitigating this vulnerability to avoid potential fines and data breach notifications.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 4 Nov 2025, 20:18 UTC

Technical details

References

Community reviews

Related threats