CVE REMEDIATION GUIDE
CISA KEV · Known exploitedHighFixed-version data available

CVE-2024-23222 remediation guide

Apple Multiple Products

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.

Open CVE record
ProductApple Multiple Products
Affected versions< 17.3, < 15.8.7, >= 16.0 < 16.7.5, >= 17.0 < 17.3, >= 12.0 < 12.7.3, >= 13.0 < 13.6.4, >= 14.0 < 14.3, < 1.0.2
Fixed versions17.3, 15.8.7, 16.7.5, 12.7.3, 13.6.4, 14.3, 1.0.2
Priority basisImmediate · CVSS 8.8 · EPSS 10.6%
01

Identify the affected asset

Confirm whether Apple Multiple Products is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: < 17.3, < 15.8.7, >= 16.0 < 16.7.5, >= 17.0 < 17.3, >= 12.0 < 12.7.3, >= 13.0 < 13.6.4, >= 14.0 < 14.3, < 1.0.2. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

CISA has listed this vulnerability in the Known Exploited Vulnerabilities catalog. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.

CVE-2024-23222 Remediation Guide | SECUFOCUS NOW