FirefoxWeb browser · Mozilla
CVE-2016-1975
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 · uneditedMultiple race conditions in dom/media/systemservices/CamerasChild.cpp in the WebRTC implementation in Mozilla Firefox before 45.0 on Windows might allow remote attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact via unknown vectors.
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 confidenceMultiple race conditions exist in the CamerasChild.cpp component of Mozilla Firefox's WebRTC implementation on Windows. These race conditions can lead to memory corruption, causing denial of service, or potentially allow unspecified further exploitation. The vulnerability affects Firefox versions prior to 45.0 on Windows systems.
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
<= 44.0.2all versionsCVSS 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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L
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.
-
Confirm Windows platformCheck the operating system by running 'systeminfo' in Command Prompt or checking system properties. This vulnerability only affects Windows systems.Affected if The system is not running Windows - the vulnerability is Windows-specific.
-
Check installed Firefox versionOpen Firefox, navigate to Help > About Firefox, or type 'about:support' in the address bar to view the version number under Application Basics.Affected if Firefox version is 44.0.2 or earlier (any version prior to 45.0 on Windows).
-
Verify WebRTC is enabledIn Firefox, type 'about:config' in the address bar, then search for 'media.peerconnection.enabled' to check if WebRTC peer connection is enabled.Affected if WebRTC peer connection is set to true (enabled) - the vulnerable CamerasChild.cpp component is only loaded when WebRTC is active.
-
Confirm CamerasChild component usageMonitor process activity or check for the presence of CamerasChild.cpp loaded in memory during WebRTC sessions. On Windows, this can be observed via process inspection tools when a website uses getUserMedia API.Affected if WebRTC getUserMedia or peer connection APIs are being used - the race conditions in CamerasChild.cpp trigger during camera access sessions.
A user is affected if running Firefox version 44.0.2 or earlier on Windows with WebRTC peer connection enabled and actively using camera/microphone features through WebRTC.
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 dataUpgrade Mozilla Firefox to version 45.0 or later, which contains the fix for these race conditions in the WebRTC systemservices component.
Fix this in Firefox
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-1975 — 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-2016-1975 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