CVE-2023-42847
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 · uneditedA logic issue was addressed with improved checks. This issue is fixed in macOS Sonoma 14.1, iOS 17.1 and iPadOS 17.1. An attacker may be able to access passkeys without authentication.
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 confidenceA logic flaw in Apple's passkey implementation allowed attackers to bypass authentication and access stored passkeys without proper verification. Passkeys are Apple's FIDO-based passwordless authentication credentials stored on device.
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.1>= 17.0, < 17.1>= 14.0, < 14.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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 versionOn the iPhone, go to Settings > General > About and note the version number shown next to 'Version'Affected if The version starts with 17.0 (17.0.x) - any version from 17.0 to 17.0.x is affected; versions 17.1 and later are patched
-
Check iPadOS versionOn the iPad, go to Settings > General > About and note the version number shown next to 'Version'Affected if The version starts with 17.0 (17.0.x) - any version from 17.0 to 17.0.x is affected; versions 17.1 and later are patched
-
Check macOS versionOn Mac, open System Settings > General > About and note the version number shown next to 'Version'Affected if The version starts with 14.0 (14.0.x) - any version from 14.0 to 14.0.x is affected; versions 14.1 and later are patched
-
Verify passkey usage on iOS or iPadOSGo to Settings > Passwords (or Settings > Passwords & Passkeys on newer iOS) and look for a 'Passkeys' section or entry indicating saved passkeysAffected if Passkeys are stored on the device - the vulnerability allows bypass of authentication to access these stored passkeys
You are affected if your device runs iOS, iPadOS 17.0 through 17.0.x or macOS 14.0 through 14.0.x AND you have passkeys saved on the device; the logic flaw allows bypass of authentication to access stored passkey credentials.
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 · scoped14.117.1
Apply the vendor-supplied security updates: iOS 17.1, iPadOS 17.1, or macOS Sonoma 14.1 to patch the authentication bypass in the passkey subsystem.
iOS 17.1 / iPadOS 17.1 / macOS Sonoma 14.1
- For iPhone: Go to Settings > General > Software Update and install iOS 17.1
- For iPad: Go to Settings > General > Software Update and install iPadOS 17.1
- For Mac: Go to System Settings > General > Software Update and install macOS Sonoma 14.1
- After updating, verify the update was successful by checking Settings > General > About for the version number
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-42847 — 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-42847 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