CVE-2023-40400
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 improved checks. This issue is fixed in tvOS 17, iOS 17 and iPadOS 17, watchOS 10, macOS Sonoma 14. A remote user may cause an unexpected app termination or arbitrary code execution.
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 remote code execution vulnerability in Apple's operating systems (iOS 17, iPadOS 17, tvOS 17, watchOS 10, macOS Sonoma 14) allows remote attackers to cause unexpected app termination or execute arbitrary code. The fix involved improved checks, likely indicating an input validation or bounds checking issue in a network-facing component.
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.6< 16.6< 14.0< 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 your Apple device typeDetermine whether the device is an iPhone, iPad, Mac, Apple TV, or Apple Watch. This is needed because version ranges differ across product lines.Affected if Device is an Apple product (iPhone, iPad, Mac, Apple TV, or Apple Watch)
-
Check iOS or iPadOS version on iPhone/iPadGo to Settings > General > About on iPhone or iPad. Note the version number displayed next to 'Software Version'.Affected if Version is earlier than 16.6 on iPhone or iPad
-
Check macOS version on MacClick the Apple menu > About This Mac. Note the version number displayed (such as 13.x, 14.x, etc.).Affected if Version is earlier than 14.0 on Mac
-
Check tvOS version on Apple TVGo to Settings > General > About > Version on Apple TV. Note the version number.Affected if Version is earlier than 17.0 on Apple TV
-
Check watchOS version on Apple WatchOpen the Watch app on paired iPhone, go to General > About, or on Apple Watch go to Settings > General > About. Note the version number.Affected if Version is earlier than 10.0 on Apple Watch
The environment is affected if the installed OS version is lower than 16.6 for iOS/iPadOS, lower than 14.0 for macOS, lower than 17.0 for tvOS, or lower than 10.0 for watchOS.
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.014.016.6
Apply the vendor-supplied OS updates: iOS 17+, iPadOS 17+, tvOS 17+, watchOS 10+, and macOS Sonoma 14+ to all affected devices.
iOS 17 / iPadOS 17 / macOS Sonoma 14 / tvOS 17 / watchOS 10
- For iPhone/iPad: Upgrade to iOS 17 or later / iPadOS 17 or later
- For Mac: Upgrade to macOS Sonoma 14 or later
- For Apple TV: Upgrade to tvOS 17 or later
- For Apple Watch: Upgrade to watchOS 10 or later
- After upgrading, verify the version in Settings > General > About (iOS/iPadOS) or System Settings > About (macOS)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-40400 — 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-40400 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