dbcve.org
FirefoxWeb browser · Mozilla

CVE-2014-1586

MEDIUM · 5.0 CVSS v2.0 Published 2014-10-15
Fix available
A fix is available. Upgrade to after 32.0 or later.
See remediation →
59/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
content/base/src/nsDocument.cpp in Mozilla Firefox before 33.0, Firefox ESR 31.x before 31.2, and Thunderbird 31.x before 31.2 does not consider whether WebRTC video sharing is occurring, which allows remote attackers to obtain sensitive information from the local camera in certain IFRAME situations by maintaining a session after the user temporarily navigates away.

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

The nsDocument.cpp component in Firefox and Thunderbird fails to properly terminate WebRTC camera sessions when a user navigates away from a page containing an iframe. An attacker can exploit this by maintaining a hidden session after navigation, allowing continued access to the local camera and capture of video without user consent or awareness.

MitigationDeploy Mozilla Firefox 33.0 or later, Firefox ESR 31.2 or later, or Thunderbird 31.2 or later to address this vulnerability.

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:<= 32.0= 30.0= 31.0= 31.1.0
ThunderbirdApplication
Affected:= 31.0= 31.1.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
Authentication
None
Confidentiality
Partial
Integrity
None
Availability
None

AV:N/AC:L/Au:N/C:P/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 installed Firefox version
    Open Firefox and navigate to Help > About Firefox, or type 'about:support' in the address bar. Note the version number displayed.
    Affected if The version is 30.0, 31.0, 31.1.0, or any version 32.0 or lower
  2. Check installed Thunderbird version
    Open Thunderbird and navigate to Help > About Thunderbird. Note the version number displayed.
    Affected if The version is 31.0 or 31.1.0
  3. Verify WebRTC peer connection status
    In the Firefox address bar, type 'about:config' and press Enter. Search for the preference 'media.peerconnection.enabled'. Check its value.
    Affected if The preference is set to 'true' (enabled), making the vulnerable WebRTC code path active
  4. Check camera or microphone permissions granted
    Navigate to Firefox preferences, then Privacy & Security > Permissions > Camera and Microphone. Review the list of websites with stored permissions.
    Affected if Any websites have been granted camera or microphone permissions, as these could be exploited through the lingering session vulnerability

You are affected if you run Firefox 30.0-32.0 or Thunderbird 31.0-31.1.0 with WebRTC (media.peerconnection.enabled) turned on and have granted any camera or microphone permissions to websites.

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 a release after 32.0
Interim mitigation

Deploy Mozilla Firefox 33.0 or later, Firefox ESR 31.2 or later, or Thunderbird 31.2 or later to address this vulnerability.

Fix this in Firefox Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-1586 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2014-1586 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