Threats / Apple / CVE-2023-42824

CVE-2023-42824 · EUVD no mirror located · GCVE no mirror located Verified 2026-09-19

Apple iOS and iPadOS vulnerability

Apple iOS and iPadOS contain an unspecified local privilege escalation vulnerability that has been exploited in the wild.

Verdict

Today item — known-exploited.

A local privilege escalation flaw in iOS and iPadOS enables attackers with device access to gain elevated system permissions. Active exploitation in the wild indicates practical threat to users, particularly those targeted by sophisticated threat actors.

CISA KEV Yes · 2023-10-05⁴EPSS 0.00935 (verify live)⁵Exploit Public PoC⁶CVSS 7.8 (CISA)³CISA SSVC Exploitation: active · Automatable: no · Impact: total³

Is it exploitable?

— the evidence, ranked above the score

Exploit available

Public proof-of-concept exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.

vulncheck.com ↗Confirmed

Reported exploitation

5 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.

docs.google.com ↗support.apple.com ↗cisa.gov ↗support.apple.com ↗Confirmed

Exploited in the wild

Listed in the CISA Known Exploited Vulnerabilities catalog (added 2023-10-05).

CISA KEV ↗Confirmed

Probability (EPSS)

EPSS 0.00935 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.

FIRST EPSS ↗High

Severity / affected

CVSS 7.8 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) · Affected: Apple, iOS and iPadOS. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.

CISA-ADP ↗Reported

CISA SSVC (triage disposition)

Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.

CISA-ADP ↗Reported

Currency of the record

CISA added this to its KEV catalog 1 day after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.

CISA KEV ↗CVE.org ↗Reported

Who’s exploiting it?

— attribution turns risk into urgency

Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

Why it matters

— the attack path, told twice: adversary, then board

Front door — unauthenticated access narrative 1

Attacker

I gain initial access to the device through a separate vulnerability or user compromise.

Business

User device security is compromised, creating entry point for further system compromise.

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker

I exploit this local privilege escalation flaw to elevate my permissions from user-level to system-level access.

Business

Attacker obtains root or kernel-level control, bypassing all application sandboxing and security boundaries.

Lateral reach — past segmentation narrative 3

Attacker

I install persistent malware, exfiltrate sensitive data, or modify system behavior without user detection.

Business

Complete device compromise enables data theft, surveillance, financial fraud, or lateral movement to enterprise networks.

What to do

— defensible action

Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.¹

Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.

Coverage & confidence

— what we know, and what we don’t

Established (cited)

KEV listing (CISA)

EPSS probability (FIRST)

Public PoC available (VulnCheck)

5 reported-exploitation source(s)

CVSS 7.8 — CISA-assigned (CVE.org ADP)

CISA SSVC triage disposition (CVE.org ADP)

Public exploit availability

Catalogued by apple (CNA)

Coverage gaps — stated, not hidden

No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.

EPSS & exposure are time-varying; verify live at the source.

Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.

No finder is named in the public CVE record or the scanned vendor advisory — attribution scoped to the sources checked.

Disclosure & credit²

Catalogued by appleCNA

Credited with finding itNo finder is named in the public CVE record or the scanned vendor advisory — attribution scoped to the sources checked.

Found an error? Propose a correction.

A correction is a cited counter-claim — it must cite a source, gets reviewed by a second human, and is never auto-applied. See the correction convention and our identity npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y.

With JavaScript off: publish a signed kind 1111 Nostr event tagging ["r", "https://basicsecurity.net/threat/cve-2023-42824.html"], ["v", "sha256:b101a2ae11ec64e5c54085fbb241fe68abdc5e5dab78d437fafc0bb891fbbd84"] (the record version), plus ["src", "<your source URL>"] and ["t", "correction"], per the correction convention. Our identity: npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y. Cite-or-die: an event with no src is a coverage finding, not a proposal.