CVE-2019-8711
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 existed with the display of notification previews. This issue was addressed with improved validation. This issue is fixed in iOS 13. Notification previews may show on Bluetooth accessories even when previews are disabled.
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 validation flaw in iOS caused notification previews to be displayed on Bluetooth accessories even when the user had disabled preview settings. The vulnerability allowed sensitive notification content to leak to paired Bluetooth devices (e.g., headphones, speakers, car kits) contrary to the user's privacy preferences.
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< 13.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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 versionGo to Settings > General > About and note the version number displayed next to 'Version'Affected if The version is any release earlier than 13.0 (for example, 12.4.1, 12.3, 11.x)
-
Verify Bluetooth is enabledGo to Settings > Bluetooth and confirm the Bluetooth toggle is turned onAffected if Bluetooth is currently enabled on the device
-
Identify paired Bluetooth accessoriesIn Settings > Bluetooth, review the list under 'My Devices' for any connected or previously paired accessories such as headphones, speakers, car kits, or smartwatchesAffected if One or more Bluetooth devices are paired or connected
-
Review notification preview settingsGo to Settings > Notifications > Show Previews and check the current setting (options include 'Always', 'When Unlocked', or 'Never')Affected if Preview setting is set to 'When Unlocked' or 'Never' (user believes previews are restricted)
-
Confirm notification content exposure via BluetoothWith a paired Bluetooth accessory connected, observe whether notification text (SMS, email, app alerts) is spoken or displayed on the Bluetooth device when the iPhone is locked, even though preview restrictions are enabledAffected if Notification content leaks to the Bluetooth accessory despite preview restrictions being configured
You are affected if your device runs iOS version earlier than 13.0, has Bluetooth enabled with paired accessories, and notice notification text appearing on Bluetooth devices despite having restricted preview settings.
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.
From vendor data13.0
Update affected iOS devices to iOS 13 or later, which contains the improved validation logic that properly enforces the user's notification preview settings across Bluetooth accessories.
- Consultation1.0 h
- Implementation2.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-8711 — 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-2019-8711 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