dbcve.org
macOSOperating system · Apple

CVE-2024-23216

HIGH · 7.1 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 →
74/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 path handling issue was addressed with improved validation. This issue is fixed in macOS Monterey 12.7.4, macOS Sonoma 14.4, macOS Ventura 13.6.5. An app may be able to overwrite arbitrary files.

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 path traversal vulnerability in macOS where insufficient path validation allows an application to potentially overwrite arbitrary files outside intended directories using path traversal sequences. The fix implements improved path validation to prevent directory escape.

MitigationUpdate to macOS Monterey 12.7.4, Ventura 13.6.5, or Sonoma 14.4. For custom applications, implement proper path validation - validate that resolved paths remain within intended directories and sanitize path traversal sequences.

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

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/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 installed macOS version
    Run 'sw_vers -productVersion' in Terminal or open System Settings > About to view the macOS version
    Affected if Version is 12.0 through 12.7.3, 13.0 through 13.6.4, or 14.0 through 14.3

You are affected if your Mac runs macOS Monterey 12.7.3 or earlier, Ventura 13.6.4 or earlier, or Sonoma 14.3 or earlier.

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

Update to macOS Monterey 12.7.4, Ventura 13.6.5, or Sonoma 14.4. For custom applications, implement proper path validation - validate that resolved paths remain within intended directories and sanitize path traversal sequences.

Recommended fix High confidence

macOS Monterey 12.7.4, macOS Ventura 13.6.5, or macOS Sonoma 14.4 (depending on your current version line)

  1. Identify your current macOS version by clicking the Apple menu and selecting About This Mac
  2. If running macOS Monterey 12.0-12.7.3, upgrade to macOS Monterey 12.7.4
  3. If running macOS Ventura 13.0-13.6.4, upgrade to macOS Ventura 13.6.5
  4. If running macOS Sonoma 14.0-14.3, upgrade to macOS Sonoma 14.4
  5. To upgrade, open System Settings, select General, then Software Update, and click Update Now
  6. Alternatively, download the appropriate Combo Update from Apple Support downloads and run it
Caveat Standard macOS update risks apply - ensure important data is backed up before updating

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

Fix this in macOS Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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