CVE-2024-23222
A type confusion issue was addressed with improved checks. This issue is fixed in Safari 17.3, iOS 15.8.7 and iPadOS 15.8.7, iOS 16.7.5 and iPadOS 16.7.5, iOS 17.3 and iPadOS 17.3, macOS Monterey 12.7.3, macOS Sonoma 14.3, macOS Ventura 13.6.4, tvOS 17.3, visionOS 1.0.2. Processing maliciously crafted web content may lead to arbitrary code execution. This fix associated with the Coruna exploit was shipped in iOS 17.3 on January 22, 2024. This update brings that fix to devices that cannot update to the latest iOS version.
- CVSS
- 8.8Highscored by CISA
- Exploited in the wild
- Yes, in CISA KEV since 23 Jan 2024CISA deadline for US federal agencies: 13 Feb 2024unvetted proof-of-concept code on github
- EPSS
- 10.6%chance of exploitation in the next 30 daystop 5% of scored CVEsFIRST score of 11 Nov 2026
- Fix
- Patch availablesee the advisories in the references
- Published
- 23 Jan 2024analysed here 12 Nov 2026
Do first. Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. (CISA's required action for this KEV entry)
Summary
Triage
- Exploitable
- At runtime
- Attack vector
- network
- Weakness
- CWE-843 Common Weakness
The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.
Affected products
| Product | Affected versions | Vendor says fixed in |
|---|---|---|
| Apple iOS and iPadOS | < 15.8.7< 16.7.5< 17.3Vendor says fixed in: not stated | |
| Apple macOS | < 12.7.3< 13.6.4< 14.3Vendor says fixed in: not stated | |
| Apple Safari | < 17.3Vendor says fixed in: not stated | |
| Apple tvOS | < 17.3Vendor says fixed in: not stated | |
| Apple visionOS | < 1.0.2Vendor says fixed in: not stated |
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
Products named in our analysis
- apple:safari
- apple:ipados
- apple:iphone_os
- apple:macos
- apple:tvos
- apple:visionos
Fix and mitigation
WAF and other mitigations
Can a WAF block it? No. The vulnerability is triggered by processing maliciously crafted web content, which is delivered via HTTP requests to the Safari browser or related Apple OS web components. The malicious content looks like normal web content, so a web application firewall cannot reliably distinguish and block it without affecting legitimate users.
Also consider: patch
Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Remediation steps (AI-written)
Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.
Exploitation evidence
- CISA KEV catalog
- Listed since 23 Jan 2024.
- CISA due date
- 13 Feb 2024, the remediation deadline for US federal agencies
- CISA required action
- Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
- Public exploit code
- Unvetted proof-of-concept code on GitHub: 3 GitHub proofs of concept
- CISA SSVC
- exploitation active, automatable no, technical impact totalAssessed by CISA 1 Feb 2024 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.
GitHub proofs of concept
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
Timeline
- 23 Jan 2024Added to CISA KEV (exploited in the wild)
- 23 Jan 2024Publishedsame day later
- 1 Feb 2024CISA SSVC assessment: exploitation active9 days later
- 13 Feb 2024CISA remediation due date (US federal agencies)12 days later
- 10 Mar 2026First proof-of-concept repository on GitHub (unvetted)756 days (about 2 years) later
- 2 Apr 2026CVE record last updated24 days later
- 12 Nov 2026Analysed by vulneraibility.com224 days (about 7 months) later
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
| Metric | Value | What it means |
|---|---|---|
| Attack vector | NetworkReachable over the internet or any routable network. | Reachable over the internet or any routable network. |
| Attack complexity | LowRepeatable attack, no special conditions. | Repeatable attack, no special conditions. |
| Privileges required | NoneThe attacker needs no prior access. | The attacker needs no prior access. |
| User interaction | RequiredA victim must click, open or otherwise cooperate. | A victim must click, open or otherwise cooperate. |
| Scope | UnchangedImpact stays within the vulnerable component. | Impact stays within the vulnerable component. |
| Confidentiality | HighTotal data disclosure possible. | Total data disclosure possible. |
| Integrity | HighComplete modification possible. | Complete modification possible. |
| Availability | HighFull outage possible. | Full outage possible. |
Common questions
Is CVE-2024-23222 being exploited?
Yes. CVE-2024-23222 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2024-23222?
CVE-2024-23222 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2024-23222?
Yes. A fix has been recorded for CVE-2024-23222. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2024-23222 affect?
CVE-2024-23222 affects apple:safari, apple:ipados, apple:iphone_os, apple:macos, and 2 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
References
25 references in the CVE record, grouped by the tags the record gives them.
Other links (25)
- support.apple.com /en-us/118479
- support.apple.com /en-us/120304
- support.apple.com /en-us/120305
- support.apple.com /en-us/120307
- support.apple.com /en-us/120309
- support.apple.com /en-us/120310
Show 19 more
- support.apple.com /en-us/120311
- support.apple.com /en-us/120339
- support.apple.com /en-us/126632
- support.apple.com /en-us/HT214059
- support.apple.com /en-us/HT214055
- support.apple.com /en-us/HT214061
- support.apple.com /kb/HT214063
- support.apple.com /kb/HT214059
- support.apple.com /kb/HT214057
- support.apple.com /kb/HT214058
- support.apple.com /kb/HT214061
- support.apple.com /kb/HT214055
- support.apple.com /kb/HT214056
- lists.fedoraproject.org /archives/list/[email protected]/message/US43EQFC2IS66EA2
- seclists.org /fulldisclosure/2024/Feb/6
- support.apple.com /kb/HT214070
- seclists.org /fulldisclosure/2024/Jan/40
- seclists.org /fulldisclosure/2024/Jan/34
- cisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-23222
Where the data on this page comes from
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
Similar CVEs
Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.