dbcve.org
macOSOperating system · Apple

CVE-2024-23268

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
An injection issue was addressed with improved input 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 elevate 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

An injection vulnerability in macOS allowed a malicious application to inject and execute arbitrary commands with elevated (root) privileges. Apple addressed this with improved input validation to sanitize user-supplied data before processing. The vulnerability affects macOS Monterey, Ventura, and Sonoma versions prior to their respective patches.

MitigationApply the appropriate macOS security update: macOS Monterey 12.7.4, macOS Ventura 13.6.5, or macOS Sonoma 14.4, depending on the macOS version in use. In enterprise environments, deploy via MDM following standard patch management procedures.

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.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. Retrieve installed macOS version
    Run `sw_vers -productVersion` in Terminal or check System Settings > About to obtain the installed macOS version number
    Affected if Command returns a version number such as 12.6.1, 13.5.2, or 14.2.1
  2. Identify macOS release family
    Note the major version number: 12.x indicates Monterey, 13.x indicates Ventura, 14.x indicates Sonoma
    Affected if The major version is 12, 13, or 14
  3. Compare against affected version ranges
    For Monterey (12.x): check if version is >= 12.0.0 and < 12.7.4. For Ventura (13.x): check if version is >= 13.0 and < 13.6.5. For Sonoma (14.x): check if version is >= 14.0 and < 14.4
    Affected if The installed version falls within any of these ranges: 12.0.0-12.7.3, 13.0-13.6.4, or 14.0-14.3

System is vulnerable if running any unpatched version of macOS Monterey prior to 12.7.4, Ventura prior to 13.6.5, or Sonoma prior to 14.4.

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: macOS Monterey 12.7.4, macOS Ventura 13.6.5, or macOS Sonoma 14.4, depending on the macOS version in use. In enterprise environments, deploy via MDM following standard patch management procedures.

Recommended fix High confidence

macOS 12.7.4 (Monterey), macOS 13.6.5 (Ventura), or macOS 14.4 (Sonoma) - depending on your starting version

  1. 1. Back up your Mac using Time Machine or another backup solution before proceeding
  2. 2. Determine your current macOS version by clicking the Apple menu > About This Mac
  3. 3. For macOS 12.x (Monterey) users: Upgrade to macOS 12.7.4 by going to System Settings > General > Software Update and installing the available update
  4. 4. For macOS 13.x (Ventura) users: Upgrade to macOS 13.6.5 by going to System Settings > General > Software Update and installing the available update
  5. 5. For macOS 14.x (Sonoma) users: Upgrade to macOS 14.4 by going to System Settings > General > Software Update and installing the available update
  6. 6. Restart your Mac when prompted to complete the installation
Caveat Standard macOS upgrade considerations apply - review release notes for any app compatibility issues 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
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
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,848.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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