CVE-2023-42887
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 · uneditedAn access issue was addressed with additional sandbox restrictions. This issue is fixed in macOS Ventura 13.6.4, macOS Sonoma 14.2. An app may be able to read 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 · moderate confidenceThis is a macOS sandbox bypass vulnerability where a malicious or compromised application could read arbitrary files outside its intended sandbox boundaries. The fix involved adding additional sandbox restrictions to prevent unauthorized file system access.
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.6.4>= 14.0, < 14.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
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Determine the installed macOS versionRun 'sw_vers -productVersion' in Terminal, or go to System Settings > General > AboutAffected if The version falls within 13.0 to 13.6.3, or 14.0 to 14.1 (unpatched)
-
Identify the major macOS release nameCheck if the system is running Ventura (13.x) or Sonoma (14.x) from the version outputAffected if Running Ventura (13.x) below 13.6.4, or Sonoma (14.x) below 14.2
-
Confirm the patch stateCheck System Settings > General > Software Update for available updates, or run 'system_profiler SPSoftwareDataType' to see installation date of updatesAffected if No security update to 13.6.4+ or 14.2+ has been installed
The system is affected if it runs macOS Ventura 13.0-13.6.3 or Sonoma 14.0-14.1 and has not received the corresponding security update.
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.6.414.2
Apply the macOS security updates (Ventura 13.6.4 or later, Sonoma 14.2 or later) to affected systems to receive the sandbox restriction fixes.
macOS Ventura 13.6.4 or macOS Sonoma 14.2
- Back up your Mac using Time Machine or another backup solution before performing system updates
- Check your current macOS version by clicking the Apple menu > About This Mac
- If running macOS Ventura (13.x), upgrade to macOS Ventura 13.6.4 via System Settings > General > Software Update
- If running macOS Sonoma (14.0-14.1), upgrade to macOS Sonoma 14.2 via System Settings > General > Software Update
- Restart your Mac when prompted to complete the installation
- Verify the update was successful by checking About This Mac shows the correct version number
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA0.5 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,280.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-42887 — 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-42887 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