dbcve.org
macOSOperating system · Apple

CVE-2024-23247

HIGH · 7.8 CVSS v3.1 Published 2024-03-08
Fix available
A fix is available. Upgrade to 12.7.4 / 13.6.5 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 macOS Monterey 12.7.4, macOS Sonoma 14.4, macOS Ventura 13.6.5. Processing a file may lead to unexpected app termination or arbitrary code execution.

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 · high confidence

A memory handling vulnerability in macOS allows arbitrary code execution or unexpected app termination when processing a maliciously crafted file. The issue was addressed with improved memory handling in the affected OS versions.

MitigationApply the appropriate macOS security update (Monterey 12.7.4, Ventura 13.6.5, or Sonoma 14.4) to patch the memory handling vulnerability.

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
macOSOperating system
Affected:>= 12.0, < 12.7.4>= 13.0, < 13.6.5>= 14.0, < 14.4

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. Identify installed macOS version
    Run 'sw_vers -productVersion' in Terminal or click Apple menu > About This Mac
    Affected if The version shown falls within the affected ranges: 12.0-12.7.3, 13.0-13.6.4, or 14.0-14.3.x
  2. Confirm macOS release name
    Run 'sw_vers -productVersionExtra' or check the macOS name corresponding to your version number (Monterey=12.x, Ventura=13.x, Sonoma=14.x)
    Affected if The system runs Monterey 12.0-12.7.3, Ventura 13.0-13.6.4, or Sonoma 14.0-14.3.x
  3. Verify patch status
    Run 'softwareupdate --history' to see if security updates including the fix have been installed
    Affected if No security update to 12.7.4, 13.6.5, or 14.4 appears in the history

You are affected if your macOS version is 12.0-12.7.3, 13.0-13.6.4, or 14.0-14.3 and the corresponding security update has not been applied.

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 12.7.4 / 13.6.5 / 14.4 or later
Fixed in 12.7.413.6.514.4
Interim mitigation

Apply the appropriate macOS security update (Monterey 12.7.4, Ventura 13.6.5, or Sonoma 14.4) to patch the memory handling vulnerability.

Recommended fix High confidence

macOS Monterey 12.7.4 / macOS Ventura 13.6.5 / macOS Sonoma 14.4 (depending on your target version)

  1. 1. Back up all important data using Time Machine or another backup solution
  2. 2. Verify your current macOS version by clicking the Apple menu and selecting About This Mac
  3. 3. Open System Settings (System Preferences on older macOS) and navigate to Software Update
  4. 4. If an update is available, click Update Now or download the specific update for your macOS version: Monterey 12.7.4, Ventura 13.6.5, or Sonoma 14.4
  5. 5. Allow the update to download and install completely
  6. 6. Restart your Mac when prompted to complete the installation
  7. 7. After restarting, verify the update was successful by checking About This Mac again
Caveat macOS upgrades may cause incompatibility with older 32-bit applications; review app compatibility before upgrading

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

Fix this in macOS Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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