Threats / Apple / CVE-2022-22587
CVE-2022-22587
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Apple iOS and macOS vulnerability
Apple IOMobileFrameBuffer memory corruption vulnerability allows malicious applications to execute arbitrary code with kernel privileges on iOS and macOS systems.
Verdict
Today item — known-exploited.
A local privilege escalation vulnerability in IOMobileFrameBuffer enables installed applications to corrupt kernel memory and gain elevated code execution capabilities, bypassing security boundaries.
CISA KEV Yes · 2022-01-284EPSS 0.11638 (verify live)5CVSS 9.8 (CISA)3CISA SSVC Exploitation: active · Automatable: yes · Impact: total3
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
7 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 2022-01-28).
Probability (EPSS)
EPSS 0.11638 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) · Affected: Apple, iOS and macOS. 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-20 Improper Input Validation, 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: yes · 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 the same day 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 craft a malicious application that exploits improper input validation in IOMobileFrameBuffer to trigger memory corruption.
Business
User installs a compromised or trojanized app from app store or third-party source, creating initial infection vector.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I leverage the memory corruption to write arbitrary data into kernel memory regions, bypassing bounds checking.
Business
Application gains unauthorized access to kernel-level operations and system resources protected by OS security model.
3
Lateral reach — past segmentation narrative 3
Attacker
I execute arbitrary code with kernel privileges, establishing persistent control over the compromised device.
Business
Attacker can access sensitive user data, install rootkits, modify system behavior, or pivot to other devices on network.
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