dbcve.org
IpadosOperating system · Apple

CVE-2024-23264

MEDIUM · 5.5 CVSS v3.1 Published 2024-03-08
Fix available
A fix is available. Upgrade to 1.1 / 12.7.4 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A validation issue was addressed with improved input sanitization. This issue is fixed in iOS 16.7.6 and iPadOS 16.7.6, iOS 17.4 and iPadOS 17.4, macOS Monterey 12.7.4, macOS Sonoma 14.4, macOS Ventura 13.6.5, tvOS 17.4, visionOS 1.1. An application may be able to read restricted memory.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

CVE-2024-23264 is a validation issue in Apple operating systems where insufficient input sanitization allows an application to read restricted memory, leading to potential information disclosure. This vulnerability affects iOS, iPadOS, macOS, tvOS, and visionOS across multiple version ranges.

MitigationApply the vendor-supplied patches by updating affected devices to iOS 16.7.6/17.4 and iPadOS 16.7.6/17.4, macOS Monterey 12.7.4/Ventura 13.6.5/Sonoma 14.4, tvOS 17.4, or visionOS 1.1 as appropriate.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
IpadosOperating system
Affected:< 16.7.6>= 17.0, < 17.4
Iphone OsOperating system
Affected:< 16.7.6>= 17.0, < 17.4
macOSOperating system
Affected:>= 12.0, < 12.7.4>= 13.0, < 13.6.5>= 14.0, < 14.4
TvosOperating system
Affected:< 17.4
VisionosOperating system
Affected:< 1.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check iOS version on iPhone
    Go to Settings > General > About and note the Version number
    Affected if Version is below 16.7.6, or is 17.0 through 17.3 (any version < 17.4 but >= 17.0, or any version < 16.7.6)
  2. Check iPadOS version on iPad
    Go to Settings > General > About and note the Version number
    Affected if Version is below 16.7.6, or is 17.0 through 17.3 (any version < 17.4 but >= 17.0, or any version < 16.7.6)
  3. Check macOS version
    Go to System Settings > About or run 'sw_vers' in Terminal and note the release version
    Affected if Version is 12.0 to 12.7.3, 13.0 to 13.6.4, or 14.0 to 14.3 (any version less than 12.7.4, 13.6.5, or 14.4 respectively)
  4. Check tvOS version
    Go to Settings > General > About and note the Version number
    Affected if Version is any version below 17.4 (any version < 17.4)
  5. Check visionOS version
    Go to Settings > About and note the Version number
    Affected if Version is any version below 1.1 (any version < 1.1)

Your device is affected if it runs any iOS, iPadOS, macOS, tvOS, or visionOS version that falls within the specified vulnerable ranges.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.1 / 12.7.4 / 13.6.5 or later
Fixed in 1.112.7.413.6.5
Interim mitigation

Apply the vendor-supplied patches by updating affected devices to iOS 16.7.6/17.4 and iPadOS 16.7.6/17.4, macOS Monterey 12.7.4/Ventura 13.6.5/Sonoma 14.4, tvOS 17.4, or visionOS 1.1 as appropriate.

Recommended fix High confidence

iOS 16.7.6 / iOS 17.4, iPadOS 16.7.6 / iPadOS 17.4, macOS Monterey 12.7.4 / Ventura 13.6.5 / Sonoma 14.4, tvOS 17.4, visionOS 1.1

  1. For iOS/iPadOS: Go to Settings > General > Software Update and install the available update to iOS 16.7.6 or iOS 17.4/iPadOS 16.7.6 or iPadOS 17.4
  2. For macOS: Go to System Settings > General > Software Update and install the available update to macOS Monterey 12.7.4, Ventura 13.6.5, or Sonoma 14.4 depending on your current macOS version
  3. For tvOS: Go to Settings > System > Software Update and install the update to tvOS 17.4
  4. For visionOS: Go to Settings > General > Software Update and install the update to visionOS 1.1
  5. After updating, verify the update was successful by checking the OS version in Settings > General > About
Caveat Apple security updates generally do not introduce breaking changes; standard upgrade risks apply (review app compatibility before updating)

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ipados Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-23264 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-23264 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data