CVE-2024-54529
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 · uneditedA logic issue was addressed with improved checks. This issue is fixed in macOS Sequoia 15.2, macOS Sonoma 14.7.2, macOS Ventura 13.7.2. An app may be able to execute arbitrary code out of its sandbox or with certain elevated 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 confidenceThis is a sandbox escape vulnerability in macOS where a logic flaw allowed a malicious application to bypass sandbox restrictions and execute arbitrary code outside its designated sandbox or with elevated privileges. The vulnerability was addressed with improved logic checks in the affected macOS versions.
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>= 13.0, < 13.7.2>= 14.0, < 14.7.2>= 15.0, < 15.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed macOS versionRun `sw_vers` in Terminal and note the ProductVersion (for example, 13.6.1, 14.5, or 15.1)Affected if Version falls between 13.0 and 13.7.1, between 14.0 and 14.7.1, or between 15.0 and 15.1 (inclusive of endpoints for lower bounds, exclusive for upper bounds)
-
Confirm version is not patchedCompare your version against the fixed releases: macOS Ventura 13.7.2, Sonoma 14.7.2, or Sequoia 15.2Affected if Your installed version is lower than the fixed release for your major macOS version
-
Verify system is running a vulnerable macOS releaseCheck System Settings > About This Mac > macOS version, or run `uname -r` to confirm the Darwin kernel versionAffected if The system runs any macOS release from the affected version ranges without the security patch
Your environment is affected if the installed macOS version is 13.0-13.7.1, 14.0-14.7.1, or 15.0-15.1, because these versions contain the vulnerable logic checks that can be exploited to escape sandbox restrictions.
Generated from the published advisory. Verify against your own configuration.
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 · scoped13.7.214.7.215.2
Apply the available macOS security updates: macOS Sequoia 15.2, macOS Sonoma 14.7.2, or macOS Ventura 13.7.2 depending on the installed version. These updates contain the patched logic checks that prevent the sandbox escape.
macOS Ventura 13.7.2, macOS Sonoma 14.7.2, or macOS Sequoia 15.2
- Back up your Mac using Time Machine or another backup solution before updating
- Open System Settings (or System Preferences on older macOS versions)
- Navigate to General > Software Update
- Allow macOS to check for updates
- If macOS Ventura 13.7.2, Sonoma 14.7.2, or Sequoia 15.2 is available, click 'Update Now' to download and install the update
- Restart your Mac when prompted to complete the installation
- Alternatively, you can download the update manually from Apple Support downloads and install it
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2024-54529 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-54529 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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