CVE-2014-8643
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 · uneditedMozilla Firefox before 35.0 on Windows allows remote attackers to bypass the Gecko Media Plugin (GMP) sandbox protection mechanism by leveraging access to the GMP process, as demonstrated by the OpenH264 plugin's process.
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 confidenceMozilla Firefox before version 35.0 on Windows contains a sandbox bypass vulnerability in the Gecko Media Plugin (GMP) subsystem. Attackers with access to the GMP process (such as the OpenH264 plugin's process) can circumvent the sandbox protection mechanism, potentially allowing execution of arbitrary code with elevated privileges.
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<= 34.0.5= 13.1= 13.2CVSS 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
- M
- Authentication
- None
- Confidentiality
- None
- Integrity
- Complete
- Availability
- None
AV:N/AC:M/Au:N/C:N/I:C/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 installed Firefox versionOpen Firefox, go to Help > About Firefox, or run 'firefox --version' from command lineAffected if Version is 34.0.5 or lower on Windows systems
-
Confirm operating system is WindowsCheck system OS - this vulnerability affects only Windows systemsAffected if Running Windows with vulnerable Firefox version
-
Verify GMP (Gecko Media Plugin) is enabledIn Firefox, check Add-ons > Plugins section for Gecko Media Plugin entries (such as OpenH264)Affected if GMP plugins are present and enabled on a vulnerable Firefox Windows installation
-
Inspect running GMP processesOpen Windows Task Manager or run 'tasklist' command and look for processes related to GMP (such as gmpopenh264.exe or similar GMP host processes)Affected if GMP process is running on a vulnerable Firefox Windows version
User is affected if running Firefox version 34.0.5 or lower on Windows with GMP plugins enabled and the GMP process active
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 dataUpdate Mozilla Firefox to version 35.0 or later on all Windows systems. This addresses the sandbox bypass in the Gecko Media Plugin by implementing proper isolation between the GMP process and privileged system resources.
- 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-2014-8643 — 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-2014-8643 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