CVE-2023-27944
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 · uneditedThis issue was addressed with a new entitlement. This issue is fixed in macOS Ventura 13.3, macOS Monterey 12.6.4, macOS Big Sur 11.7.5. An app may be able to break out of its sandbox.
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 confidenceA sandbox escape vulnerability in macOS where a malicious or compromised application could break out of its sandbox and potentially access resources outside its permitted boundaries. The issue was addressed by introducing a new entitlement in macOS Ventura 13.3, Monterey 12.6.4, and Big Sur 11.7.5.
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< 11.7.5>= 12.0, < 12.6.4>= 13.0, < 13.3CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/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.
-
Identify installed macOS versionRun 'sw_vers -productVersion' in Terminal to get the exact macOS version numberAffected if version is < 11.7.5, OR between 12.0-12.6.3, OR between 13.0-13.2.x
-
Confirm macOS release nameCheck if the version corresponds to Big Sur (11.x), Monterey (12.x), or Ventura (13.x) using the sw_vers outputAffected if running Big Sur, Monterey, or Ventura and version falls outside the fixed releases
-
Verify sandbox is in useCheck if any applications are running with sandbox entitlements by reviewing app configurations or using 'ps' commands to observe sandboxed processesAffected if sandboxed applications are running on a vulnerable macOS version
You are affected if your macOS version is less than 11.7.5, between 12.0-12.6.3, or between 13.0-13.2.x and you run sandboxed applications.
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 · scoped11.7.512.6.413.3
Apply the appropriate macOS security update (Ventura 13.3+, Monterey 12.6.4+, or Big Sur 11.7.5+) to receive the new entitlement that prevents sandbox escape.
macOS Big Sur 11.7.5, macOS Monterey 12.6.4, or macOS Ventura 13.3 (depending on installed major version)
- Determine current macOS version by clicking Apple menu > About This Mac
- For macOS Big Sur 11.x users: Upgrade to macOS Big Sur 11.7.5 or later via Software Update
- For macOS Monterey 12.x users: Upgrade to macOS Monterey 12.6.4 or later via Software Update
- For macOS Ventura 13.x users: Upgrade to macOS Ventura 13.3 or later via Software Update
- After upgrading, verify the system is running a fixed version by checking About This Mac
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-27944 — 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-2023-27944 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