CVE-2023-28206
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 out-of-bounds write issue was addressed with improved input validation. This issue is fixed in macOS Monterey 12.6.5, iOS 16.4.1 and iPadOS 16.4.1, macOS Ventura 13.3.1, iOS 15.7.5 and iPadOS 15.7.5, macOS Big Sur 11.7.6. An app may be able to execute arbitrary code with kernel privileges. Apple is aware of a report that this issue may have been actively exploited.
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 · high confidenceAn out-of-bounds write vulnerability in the macOS/iOS kernel allows a malicious application to escalate privileges and execute arbitrary code with kernel-level access. The issue was addressed through improved input validation in the patched OS 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< 15.7.5>= 16.0, < 16.4.1< 15.7.5>= 16.0, < 16.4.1< 11.7.6>= 12.0, < 12.6.5>= 13.0, < 13.3.1CVSS 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.
-
Check iOS versionOn the iOS device, go to Settings > General > About and note the version number displayed next to 'Version'Affected if The version is less than 15.7.5, or greater than or equal to 16.0 but less than 16.4.1
-
Check iPadOS versionOn the iPadOS device, go to Settings > General > About and note the version number displayed next to 'Version'Affected if The version is less than 15.7.5, or greater than or equal to 16.0 but less than 16.4.1
-
Check macOS version via System SettingsClick the Apple menu > System Settings > About (or System Preferences > About on older macOS). Note the version number under 'macOS'Affected if The version is less than 11.7.6; or 12.0 to 12.6.4; or 13.0 to 13.3.0
-
Check macOS version via command lineOpen Terminal and run 'sw_vers' to display the macOS version, or 'system_profiler SPSoftwareDataType' for detailed OS informationAffected if The version displayed matches any of the affected macOS ranges: < 11.7.6, >= 12.0 < 12.6.5, or >= 13.0 < 13.3.1
A device is affected if it runs iOS, iPadOS, or macOS versions that fall within the vulnerable ranges, making it susceptible to kernel-level code execution after a malicious app escapes 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 · scoped11.7.612.6.513.3.1
Apply the appropriate OS update (macOS Monterey 12.6.5+, iOS 16.4.1+/15.7.5+, macOS Ventura 13.3.1+, macOS Big Sur 11.7.6+) to all affected devices to remediate the kernel privilege escalation vulnerability.
iOS 15.7.5/iPadOS 15.7.5 or iOS 16.4.1/iPadOS 16.4.1 for Apple mobile devices; macOS Big Sur 11.7.6, macOS Monterey 12.6.5, or macOS Ventura 13.3.1 for Macs
- Identify the currently installed iOS/iPadOS/macOS version on the device
- For iPhone and iPad: Go to Settings > General > Software Update and install iOS 15.7.5 (for devices on 15.x) or iOS 16.4.1 (for devices on 16.x)
- For Mac: Open System Settings > General > Software Update and install the appropriate security update: macOS Big Sur 11.7.6, macOS Monterey 12.6.5, or macOS Ventura 13.3.1
- Verify the update was successfully installed by checking the OS version in Settings/About
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-28206 — 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-28206 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