CVE-2024-23206
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 access issue was addressed with improved access restrictions. This issue is fixed in Safari 17.3, iOS 16.7.5 and iPadOS 16.7.5, iOS 17.3 and iPadOS 17.3, macOS Sonoma 14.3, tvOS 17.3, watchOS 10.3. A maliciously crafted webpage may be able to fingerprint the user.
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 malicious webpage can exploit an access control weakness to fingerprint users by accessing restricted browser APIs or device information that should be blocked. The vulnerability allows collection of identifying information about the user without their consent.
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.3> 16.0, < 16.7.5> 17.0, < 17.3> 16.0, < 16.7.5> 17.0, < 17.3< 14.3< 17.3< 10.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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/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.
-
Identify Safari browser version on the deviceOpen Safari, go to Safari menu > About Safari to view the version numberAffected if Version is less than 17.3
-
Check iOS version on iPhoneGo to Settings > General > About to view iOS versionAffected if Version is greater than 16.0 and less than 16.7.5, OR greater than 17.0 and less than 17.3
-
Check iPadOS version on iPadGo to Settings > General > About to view iPadOS versionAffected if Version is greater than 16.0 and less than 16.7.5, OR greater than 17.0 and less than 17.3
-
Check macOS version on MacGo to Apple menu > About This Mac to view macOS versionAffected if Version is less than 14.3 (Sonoma)
-
Check tvOS version on Apple TVGo to Settings > General > About to view tvOS versionAffected if Version is less than 17.3
-
Check watchOS version on Apple WatchOn iPhone, open Watch app > General > About to view watchOS versionAffected if Version is less than 10.3
If the device runs any affected Safari, iOS, iPadOS, macOS, tvOS, or watchOS version below the fixed releases, the access control weakness allowing user fingerprinting is present.
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.314.316.7.5
Update affected Apple devices to Safari 17.3, iOS/iPadOS 16.7.5 or 17.3, macOS Sonoma 14.3, tvOS 17.3, or watchOS 10.3 to apply the improved access restrictions.
Safari 17.3; iOS 16.7.5 / iOS 17.3; iPadOS 16.7.5 / iPadOS 17.3; macOS Sonoma 14.3; tvOS 17.3; watchOS 10.3
- Check current Safari version via Safari > About Safari (macOS) or Settings > Safari > About (iOS/iPadOS)
- Check current macOS version via Apple menu > About This Mac
- Check current iOS/iPadOS version via Settings > General > About
- Check current tvOS version via Settings > General > About > Version
- Check current watchOS version via Settings > General > About > Version
- For macOS: Install macOS Sonoma 14.3 or later via System Settings > General > Software Update
- For iOS/iPadOS: Install iOS/iPadOS 17.3 or iOS/iPadOS 16.7.5 via Settings > General > Software Update
- For Safari: Update to Safari 17.3 via macOS Software Update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-23206 — 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 sources- support.apple.com
- support.apple.com
- support.apple.com
- support.apple.com
- support.apple.com
- support.apple.com
- seclists.org
- seclists.org
- seclists.org
- seclists.org
- seclists.org
- seclists.org
- support.apple.com
- support.apple.com
- support.apple.com
- support.apple.com
- support.apple.com
- support.apple.com
- www.openwall.com
- lists.fedoraproject.org
- lists.fedoraproject.org
- support.apple.com
- support.apple.com
- support.apple.com
- support.apple.com
- support.apple.com
- support.apple.com
- nvd.nist.gov
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-23206 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