CVE-2023-27955
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 · uneditedThe issue was addressed with improved checks. This issue is fixed in macOS Ventura 13.3, iOS 16.4 and iPadOS 16.4, macOS Monterey 12.6.4, tvOS 16.4, macOS Big Sur 11.7.5. 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 confidenceA vulnerability in Apple's platforms allowed a malicious or compromised application to bypass sandbox restrictions and read arbitrary files on the filesystem. The issue stemmed from insufficient access control checks in a system component, which was addressed with improved validation logic.
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< 16.4< 16.4>= 11.0, < 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
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Check iOS/iPadOS versionGo to Settings > General > About on iOS/iPadOS, or run 'sw_vers' on macOS, to determine the installed OS versionAffected if The version is iOS < 16.4, iPadOS < 16.4, macOS 11.0 to < 11.7.5, 12.0 to < 12.6.4, or 13.0 to < 13.3
-
Identify untrusted third-party applicationsReview installed applications from unknown or unverified developers, particularly those requesting broad file access permissionsAffected if Untrusted or compromised applications with file access capabilities are installed on the device
-
Audit application sandbox behaviorMonitor which applications have accessed files outside their designated sandbox containers, using system logs or endpoint detection tools if availableAffected if Any application has accessed files outside its expected sandbox boundaries
-
Review system component access controlsExamine system logs for attempts to access protected filesystem locations from third-party applicationsAffected if Evidence exists of applications successfully accessing protected system directories or user files outside their sandbox
Your environment is affected if the device runs an unpatched iOS/iPadOS version below 16.4 or macOS versions 11.7.4 and earlier, 12.6.3 and earlier, or 13.2 and earlier, and untrusted or malicious applications have been installed that could exploit this sandbox bypass to read arbitrary files.
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 relevant security update for the affected Apple operating system version (macOS Ventura 13.3+, iOS/iPadOS 16.4+, macOS Monterey 12.6.4+, macOS Big Sur 11.7.5+, tvOS 16.4+) to patch the file access validation flaw.
macOS Big Sur 11.7.5 / macOS Monterey 12.6.4 / macOS Ventura 13.3 / iOS 16.4 / iPadOS 16.4 (depending on current version)
- Back up important data before initiating the OS upgrade
- Determine the current macOS version by clicking the Apple menu and selecting About This Mac
- For macOS Big Sur 11.0-11.7.4 users: Upgrade to macOS Big Sur 11.7.5
- For macOS Monterey 12.0-12.6.3 users: Upgrade to macOS Monterey 12.6.4
- For macOS Ventura 13.0-13.2 users: Upgrade to macOS Ventura 13.3
- For iOS/iPadOS devices: Upgrade to iOS 16.4 or iPadOS 16.4
- After upgrade, verify the system is running the patched version in Settings > General > About (iOS/iPadOS) or System Settings > General > About (macOS)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-27955 — 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-27955 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