Threats / Apple / CVE-2024-23296
CVE-2024-23296
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Apple Multiple Products vulnerability
Apple RTKit memory corruption vulnerability (CWE-787) allows attackers with kernel-level access to bypass memory protections across iOS, iPadOS, macOS, tvOS, and watchOS.
Verdict
Today item — known-exploited.
A kernel-level memory corruption flaw in RTKit enables privilege escalation and memory protection bypass for attackers already possessing arbitrary kernel read/write capabilities. Active exploitation observed despite low EPSS score.
CISA KEV Yes · 2024-03-064EPSS 0.01411 (verify live)5CVSS 7.8 (CISA)3CISA SSVC Exploitation: active · Automatable: no · Impact: total3
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
10 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).
Probability (EPSS)
EPSS 0.01411 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
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, Multiple Products. 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.
Weakness (CWE)
Mapped to CWE-787 Out-of-bounds Write — weakness family: Memory safety.CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.
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.
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.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution 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 board1
Front door — unauthenticated access narrative 1
Attacker
I exploit a prior kernel vulnerability to gain arbitrary read/write access to kernel memory.
Business
Initial compromise of device kernel integrity creates foundation for persistent, privileged attacks.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I leverage the RTKit memory corruption flaw to bypass kernel memory protections and sandbox boundaries.
Business
Security isolation mechanisms fail, allowing lateral movement and escalation across system components.
3
Lateral reach — past segmentation narrative 3
Attacker
I achieve persistent code execution with full kernel privileges across the compromised device.
Business
Complete device compromise enables data exfiltration, malware installation, and loss of confidentiality and integrity.
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