An out-of-bounds write issue was addressed with improved bounds checking.
Apple products are exposed to this out-of-bounds write: iOS and iPadOS before 15.4, macOS before 12.3, and watchOS before 8.6, 15.5, and 11.6. Vendor severity is not given. Fixes are listed per product.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Actively exploited
- Fix
- Fixed in 15.4, 12.3, 8.6, 15.5, 11.6
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Apple's tvOS, watchOS, macOS, iOS, and iPadOS are affected by a memory flaw that lets an application write data outside its allowed memory bounds. Exploiting it could allow that application to run arbitrary code with kernel-level privileges, giving it control over the entire system.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
An out-of-bounds write issue was addressed with improved bounds checking. This issue is fixed in tvOS 15.5, watchOS 8.6, macOS Big Sur 11.6.6, macOS Monterey 12.3.1, iOS 15.4.1 and iPadOS 15.4.1. An 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..
Timeline
- Added to CISA KEV
CISA has evidence of exploitation in the wild
- CISA remediation deadline
Due date for US federal agencies to patch
- CVE published
- Record last updated
- EPSS reached 10%
FIRST estimates at least a 10% chance of exploitation in the next 30 days
Affected versions
- Apple iOS and iPadOS
From unspecified · fixed in 15.4
- Apple macOS
From unspecified · fixed in 12.3
- Apple watchOS
From unspecified · fixed in 8.6
- Apple watchOS
From unspecified · fixed in 15.5
- Apple watchOS
From unspecified · fixed in 11.6
References 5
Questions about CVE-2022-22675
What does this mean?
The bug is an out-of-bounds write, where a program writes data outside the memory area it should stay within. Apple's advisory says an application may be able to run arbitrary code with kernel privileges.Source: support.apple.com, support.apple.com, support.apple.com
Am I affected, and how do I check?
Apple lists affected versions as iOS and iPadOS before 15.4, macOS before 12.3, and watchOS before 8.6, 15.5, and 11.6. The advisory's conditions name macOS Big Sur and Monterey, iPhone 6s and later, and listed iPad and iPod touch models. Check the installed software version in each device's system settings or About screen.Source: support.apple.com, support.apple.com, support.apple.com
What should I do about it?
Install the fixed release for each product: iOS and iPadOS 15.4, macOS 12.3, or the watchOS fix matching the watch's version line (8.6, 15.5, or 11.6). The advisory lists macOS Big Sur 11.6.6 as the fixed release for that macOS line.Source: support.apple.com, support.apple.com, support.apple.com
Is it being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-04-04, which means it has evidence of attacks. No public exploit code is tracked.Source: cisa.gov, cve.now feed data