CyberSecBulletin
CVE-2024-23246NVD status: Modified

This issue was addressed by removing the vulnerable code.

Published Updated By the CyberSecBulletin desk

CVE-2024-23246 is a high-severity improper input validation vulnerability in iOS and iPadOS from Apple, with a CVSS 3.1 base score of 8.6 out of 10. It can be exploited with local access to the system by an unauthenticated attacker, but only if a user takes part, for example by opening a link or file. The record lists versions 16.7.6, 17.4 as the first without the flaw, so updating iOS and iPadOS to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.69% chance of exploitation within 30 days, higher than 53% of scored CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update iOS and iPadOS to 16.7.6 or 17.4, whichever matches your release line, or a later version.
  2. Update macOS to 14.4 or a later version.
  3. Update tvOS to 17.4 or a later version.
  4. Read the advisory on support.apple.com for workarounds and exact fixed builds.
  5. Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.

Affected products and versions

VendorProductAffected versionsFixed in
AppleiOS and iPadOSbefore 16.7.6; before 17.416.7.6, 17.4
ApplemacOSbefore 14.4; 14.0 up to, but not including, 14.414.4
AppletvOSbefore 17.417.4
ApplevisionOSbefore 1.11.1
ApplewatchOSbefore 10.410.4
Appleiphone_os16.7 up to, but not including, 16.7.6; 17.0 up to, but not including, 17.416.7.6, 17.4
Appleipad_os16.7 up to, but not including, 16.7.6; 17.0 up to, but not including, 17.416.7.6, 17.4
Applesafaribefore 17.417.4
Webkitgtkwebkitgtkbefore 2.45.22.45.2
AppleiPadOSbefore 16.7.6; 17.0 up to, but not including, 17.416.7.6, 17.4

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
RequiredA user must take an action such as opening a file or link.
Scope
ChangedThe attack can reach beyond the vulnerable component into other systems.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.18.6HighNVD
CVSS 3.18.1HighCISA (ADP)

Official description

This issue was addressed by removing the vulnerable code. This issue is fixed in iOS 16.7.6 and iPadOS 16.7.6, iOS 17.4 and iPadOS 17.4, macOS Sonoma 14.4, tvOS 17.4, visionOS 1.1, watchOS 10.4. An app may be able to break out of its sandbox.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Improper Input Validation

The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

How developers prevent this class of flaw

  • Consider using language-theoretic security (LangSec) techniques that characterize inputs using a formal language and build recognizers for that language. This effectively requires parsing to be a distinct layer that effectively enforces a boundary between raw input and internal data representations, instead of allowing parser code to be scattered throughout the program, where it could be subject to errors or inconsistencies that create weaknesses.
  • Use an input validation framework such as Struts or the OWASP ESAPI Validation API. Note that using a framework does not automatically address all input validation problems; be mindful of weaknesses that could arise from misusing the framework itself (CWE-1173).
  • Understand all the potential areas where untrusted inputs can enter the product, including but not limited to: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide data to the application. Remember that such inputs may be obtained indirectly through API calls.

More Improper Input Validation vulnerabilities (CWE-20)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Third-party and government advisories

Other vulnerabilities in iOS and iPadOS

All iOS and iPadOS vulnerabilities

Recent Improper Input Validation vulnerabilities

Spotted an error? Tell us.