FirefoxWeb browser · Mozilla

CVE-2020-6812

MEDIUM · 5.3 CVSS v3.1 Published 2020-03-25
Fix available
A fix is available. Upgrade to 68.6.0 / 74.0 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
The first time AirPods are connected to an iPhone, they become named after the user's name by default (e.g. Jane Doe's AirPods.) Websites with camera or microphone permission are able to enumerate device names, disclosing the user's name. To resolve this issue, Firefox added a special case that renames devices containing the substring 'AirPods' to simply 'AirPods'. This vulnerability affects Thunderbird < 68.6, Firefox < 74, Firefox < ESR68.6, and Firefox ESR < 68.6.

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 confidence

Websites with camera or microphone permission can enumerate device names. When AirPods first connect to an iPhone, they default to the user's name in the device name (e.g., 'Jane Doe's AirPods'), allowing malicious websites to enumerate and disclose the user's full name through the WebRTC device enumeration API.

MitigationUpdate affected products to fixed versions: Thunderbird to 68.6+, Firefox to 74+, or Firefox ESR to 68.6+. This patches the device enumeration API to rename AirPods devices to just 'AirPods' without the user's name.

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
FirefoxWeb browser
Affected:< 74.0
Firefox EsrWeb browser
Affected:< 68.6.0
Ubuntu LinuxOperating system
Affected:= 16.04= 18.04= 19.10
ThunderbirdApplication
Affected:< 68.6.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Mozilla Firefox version
    Open Firefox, navigate to Help > About Firefox, or go to about:support in the address bar. Locate the 'Version' field.
    Affected if Version is below 74.0 (for regular Firefox) or below 68.6.0 (for Firefox ESR)
  2. Check Mozilla Thunderbird version
    Open Thunderbird, navigate to Help > About Thunderbird. Locate the 'Version' field.
    Affected if Version is below 68.6.0
  3. Verify Ubuntu browser package version (if Firefox came pre-installed)
    Run 'dpkg -l firefox' or 'apt-cache policy firefox' in terminal to check the installed Firefox package version.
    Affected if Ubuntu version is 16.04, 18.04, or 19.10 and Firefox version is below 74.0 (or below 68.6.0 for ESR packages)
  4. Confirm presence of Bluetooth audio devices with user name
    Check paired Bluetooth audio devices (such as AirPods) in your device settings. Look for device names that include your full name (for example, 'John Smith's AirPods').
    Affected if You have Bluetooth audio devices with your full name embedded in the device name, and the browser version is vulnerable as checked above

Your environment is affected if you run Firefox below 74.0 (or Firefox ESR/Thunderbird below 68.6.0) and have Bluetooth audio devices with your personal name in the device name, allowing websites to extract your identity via WebRTC device enumeration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 68.6.0 / 74.0 or later
Fixed in 68.6.074.0
Interim mitigation

Update affected products to fixed versions: Thunderbird to 68.6+, Firefox to 74+, or Firefox ESR to 68.6+. This patches the device enumeration API to rename AirPods devices to just 'AirPods' without the user's name.

Fix this in Firefox Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-6812 — 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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-6812 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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