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

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-283EPSS 0.11638 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported 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).
CISA KEV ↗Confirmed
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
Affected: Apple, iOS and macOS. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
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; the weakness class drives how the flaw is exploited.
NVD ↗Reported
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 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

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • 7 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.