IRONSMITHINTEL
CRITICALCVSS9.8
|
Actively Exploited
|CISA KEV|CVE-2022-22587|Auth: none — unauthenticated|Reboot: required|Manual only

Apple Memory Corruption Vulnerability (CVE-2022-22587)

Apple IOMobileFrameBuffer contains a memory corruption vulnerability which can allow a malicious application to execute arbitrary code with kernel privileges.

Published Mar 18, 2022 · Updated May 17, 2026
Why patchRisk explained in plain English
Worst-case scenarioIf unpatched

A remote attacker, without authentication, can achieve full data confidentiality loss, arbitrary modification of data, complete denial of service or system unavailability. Federal agencies are required to remediate by 2022-02-11 under CISA BOD 22-01.

How the attack worksNo clicks needed

This is a Out-of-bounds Write (CWE-787) vulnerability in Apple iOS and macOS. A memory corruption issue was addressed with improved input validation. This issue is fixed in iOS 15.3 and iPadOS 15.3, macOS Big Sur 11.6.3, macOS Monterey 12.2. A malicious application may be able to execute arbitrary code with kernel privileges. Apple is aware of a report that this issue may have been actively exploited.. Exploitation requires remote network access, low attack complexity, no authentication required, and no user interaction required.

📧

Phishing link

→

🖼

Malicious file

🔓

Server compromised

Am I affected?Quick check

Probably yes if any of these apply:

●Apple Device Administrators
●Endpoint Security
●IT Security
●Running ipados: v < 15.3; iphone os: v < 15.3; macos: v < 11.6.3, 12.0 ≤ v < 12.2
Real-world incidentsWhat we've seen

CISA added this CVE to the Known Exploited Vulnerabilities catalog on 2022-01-28 based on evidence of active exploitation in the wild. Federal agencies required to remediate by 2022-02-11.

How to patch

Manual remediation steps

1
Identify affected hosts: query inventory for os installs in scope.
2
Apply the vendor security update referenced in CVE-2022-22587's advisory. No specific KB/version is encoded yet — consult the linked MSRC/vendor URL.
3
Verify the fix per the vendor's published verification steps.
4
Document the remediation in your change ticket and re-scan with your vulnerability scanner to confirm closure.
PowerShell automationComing soon

No tested PowerShell script for this entry yet. We’re prioritising automation based on user demand.

References

↗ CVE-2022-22587↗ MSRC Advisory↗ NVD↗ Vendor Advisory