basicsecurity.net
Proof, not just disclosure.
Threats / Apple / CVE-2024-23225
CVE-2024-23225 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

Apple Multiple Products vulnerability

Apple kernel memory corruption vulnerability (CWE-787) affecting iOS, iPadOS, macOS, tvOS, watchOS, and visionOS allows attackers with kernel-level access to bypass memory protections.

Verdict

Today item — known-exploited.

A kernel memory corruption flaw in multiple Apple platforms enables privilege escalation and security control bypass for attackers who achieve initial kernel code execution. Active exploitation observed in the wild.

CISA KEV Yes · 2024-03-063EPSS 0.01481 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
8 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2024-03-06).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.01481 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Apple, Multiple Products. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-787 Out-of-bounds Write — weakness family: Memory safety.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
WeaknessCWE-787 · Out-of-bounds WriteMemory safety
02

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.

03

Why it matters

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

Front door — unauthenticated access narrative 1

Attacker
I exploit a separate vulnerability to gain initial kernel code execution on the target device.
Business
Attackers establish a foothold in the kernel execution context, bypassing user-space isolation.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I leverage the memory corruption flaw to read and write arbitrary kernel memory, circumventing kernel memory protections.
Business
Security boundaries designed to protect kernel integrity are rendered ineffective.
3

Lateral reach — past segmentation narrative 3

Attacker
I modify kernel data structures to escalate privileges or disable security mechanisms.
Business
Complete compromise of device security posture; attacker gains unrestricted system control.
04

What to do

— defensible action
  • Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
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.
05

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • 8 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • 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/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by appleCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.