dbcve.org
IpadosOperating system · Apple

CVE-2024-23212

HIGH · 7.8 CVSS v3.1 Published 2024-01-23
Fix available
A fix is available. Upgrade to 10.3 / 12.7.3 or later.
See remediation →
81/100
Remediation priority · High
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
The issue was addressed with improved memory handling. This issue is fixed in 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, watchOS 10.3. An app may be able to execute arbitrary code with kernel privileges.

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

Memory handling vulnerability in Apple operating systems that allows a malicious application to escalate privileges and execute arbitrary code with kernel-level access. The issue was addressed with improved memory handling in the vendor patches.

MitigationApply vendor-supplied patches: iOS 17.3/iPadOS 17.3 (or 16.7.5 for older devices), macOS Sonoma 14.3/Ventura 13.6.4/Monterey 12.7.3, tvOS 17.3, and watchOS 10.3. Avoid installing untrusted applications as the attack vector requires a malicious app to be present on the device.

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.0, < 16.7.5> 17.0, < 17.3
Iphone OsOperating system
Affected:> 16.0, < 16.7.5> 17.0, < 17.3
macOSOperating system
Affected:>= 12.0, < 12.7.3>= 13.0, < 13.6.4>= 14.0, < 14.3
TvosOperating system
Affected:< 17.3
WatchosOperating system
Affected:< 10.3

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
High
Availability
High

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

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 on the iPhone device and note the version number shown next to 'Version'
    Affected if The version is greater than 16.0 and less than 16.7.5, OR greater than 17.0 and less than 17.3
  2. Check iPadOS version on iPad
    Go to Settings > General > About on the iPad device and note the version number shown next to 'Version'
    Affected if The version is greater than 16.0 and less than 16.7.5, OR greater than 17.0 and less than 17.3
  3. Check macOS version
    Click the Apple menu > About This Mac and note the version number displayed (for example, 14.2, 13.5, 12.6)
    Affected if The version is 12.0 or higher but lower than 12.7.3, OR 13.0 or higher but lower than 13.6.4, OR 14.0 or higher but lower than 14.3
  4. Check tvOS version
    Go to Settings > General > About > Version on the Apple TV device
    Affected if The version is lower than 17.3
  5. Check watchOS version
    Open the Watch app on iPhone, go to My Watch > General > About, and note the watchOS version
    Affected if The version is lower than 10.3

You are affected if your Apple device runs any version within the vulnerable ranges listed above for your specific operating system.

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 10.3 / 12.7.3 / 13.6.4 or later
Fixed in 10.312.7.313.6.4
Interim mitigation

Apply vendor-supplied patches: iOS 17.3/iPadOS 17.3 (or 16.7.5 for older devices), macOS Sonoma 14.3/Ventura 13.6.4/Monterey 12.7.3, tvOS 17.3, and watchOS 10.3. Avoid installing untrusted applications as the attack vector requires a malicious app to be present on the device.

Recommended fix High confidence

iOS/iPadOS 16.7.5, iOS/iPadOS 17.3, macOS 12.7.3, macOS 13.6.4, macOS 14.3, tvOS 17.3, or watchOS 10.3 (depending on product line)

  1. Identify the current OS version on the affected device (iPhone, iPad, Mac, Apple TV, or Apple Watch)
  2. Back up important data on the device before upgrading
  3. For iPhone/iPad: Navigate to Settings > General > Software Update and upgrade to iOS/iPadOS 16.7.5 (for 16.x versions) or iOS/iPadOS 17.3 (for 17.x versions)
  4. For Mac: Open System Settings > General > Software Update and upgrade to macOS 12.7.3 (Monterey), 13.6.4 (Ventura), or 14.3 (Sonoma) depending on current version
  5. For Apple TV: Go to Settings > System > Software Updates and upgrade to tvOS 17.3
  6. For Apple Watch: Open the Watch app on iPhone, go to General > Software Update and upgrade to watchOS 10.3
  7. After upgrade, verify the device is running the fixed version in Settings/About
Caveat Standard OS upgrade considerations apply - review app compatibility and ensure backups exist before proceeding

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

Fix this in Ipados Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-23212 — 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-23212 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