CVE-2023-40410
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 read was addressed with improved input validation. This issue is fixed in macOS Ventura 13.6, tvOS 17, macOS Monterey 12.7, watchOS 10, iOS 17 and iPadOS 17, macOS Sonoma 14. An app may be able to disclose kernel memory.
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 confidenceOut-of-bounds read vulnerability in kernel components (likely IOService or similar) allows a malicious application to read kernel memory. The issue was addressed with improved input validation. This is a local privilege escalation/information disclosure vulnerability requiring a malicious app to be executed.
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< 17.0< 17.0>= 12.0.0, < 12.7>= 13.0, < 13.6< 17.0< 10.0CVSS 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 macOS versionOpen Terminal and run: sw_vers -productVersionAffected if Version is 12.0.0 through 12.6.x OR 13.0 through 13.5.x (these ranges are vulnerable)
-
Check iOS versionGo to Settings > General > About on the deviceAffected if Version is less than 17.0 (vulnerable)
-
Check iPadOS versionGo to Settings > General > About on the deviceAffected if Version is less than 17.0 (vulnerable)
-
Check tvOS versionGo to Settings > General > About on the Apple TVAffected if Version is less than 17.0 (vulnerable)
-
Check watchOS versionGo to Settings > General > About on the Apple Watch via iPhone Watch appAffected if Version is less than 10.0 (vulnerable)
The system is affected if it runs any macOS version 12.0.0-12.6.x or 13.0-13.5.x, or any iOS/iPadOS/tvOS version below 17.0, or any watchOS version below 10.0.
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 · scoped10.012.713.6
Apply the appropriate Apple security update: macOS Ventura 13.6, macOS Monterey 12.7, macOS Sonoma 14, tvOS 17, watchOS 10, iOS 17, or iPadOS 17 to affected devices.
iOS 17, iPadOS 17, tvOS 17, watchOS 10, macOS Monterey 12.7, macOS Ventura 13.6, or macOS Sonoma 14 (depending on which macOS major version is currently installed)
- Identify the current OS version on the affected device (iOS, iPadOS, macOS, tvOS, or watchOS)
- For iPhone/iPad: Go to Settings > General > Software Update and install iOS 17 or iPadOS 17
- For Mac: Open System Settings > General > Software Update and install the appropriate fixed version (Monterey 12.7, Ventura 13.6, or Sonoma 14)
- For Apple TV: Go to Settings > General > Software Update and install tvOS 17
- For Apple Watch: Open the Watch app on iPhone, go to General > Software Update and install watchOS 10
- Restart the device after the update completes
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-40410 — 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-40410 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