dbcve.org
macOSOperating system · Apple

CVE-2024-44135

MEDIUM · 5.5 CVSS v3.1 Published 2024-09-17
Fix available
A fix is available. Upgrade to 14.7 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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 permissions issue was addressed with additional restrictions. This issue is fixed in macOS Sequoia 15, macOS Sonoma 14.7. An app may be able to access protected files within an App Sandbox container.

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

This is a sandbox escape vulnerability in macOS where a sandboxed application could access protected files outside its intended container boundaries due to insufficient permission restrictions. The flaw allows a malicious or compromised app to bypass App Sandbox controls and read files it should not have access to.

MitigationApply the macOS security update by upgrading to macOS Sequoia 15 or macOS Sonoma 14.7. This is a system-level patch that requires no application code changes.

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:< 14.7

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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 installed macOS version
    Go to Apple menu > About This Mac, or run 'sw_vers' in Terminal
    Affected if The version shown is earlier than 14.7 (for example, 14.6.1, 14.5, or any version < 14.7)
  2. Confirm macOS release name
    Run 'sw_vers -productVersion' or check the About This Mac window for the macOS name (Sonoma, Ventura, etc.)
    Affected if The system is running macOS Sonoma earlier than 14.7, or any older macOS version

If the macOS version is below 14.7, the system is vulnerable to this sandbox escape flaw.

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 14.7 or later
Fixed in 14.7
Interim mitigation

Apply the macOS security update by upgrading to macOS Sequoia 15 or macOS Sonoma 14.7. This is a system-level patch that requires no application code changes.

Recommended fix High confidence

macOS Sonoma 14.7 or macOS Sequoia 15

  1. Back up important data before performing any system upgrade
  2. Open System Settings (or System Preferences on older macOS versions)
  3. Navigate to General > Software Update
  4. Check for available updates - macOS Sonoma 14.7 or macOS Sequoia 15 should appear
  5. Click 'Update Now' or 'Upgrade Now' to download and install the update
  6. Restart the Mac when prompted to complete the installation
  7. After restart, verify the update by going to Apple menu > About This Mac to confirm the version
Caveat Standard macOS upgrade considerations apply - some older applications may not be compatible; 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
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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