FirefoxWeb browser · Mozilla
CVE-2016-2810
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 46.0 on Android before 5.0 allows attackers to bypass intended Signature access requirements via a crafted application that leverages content-provider permissions, as demonstrated by reading the browser history or a saved password.
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 crafted Android application can bypass intended Signature access requirements in Mozilla Firefox for Android before version 46.0 on Android before 5.0, allowing unauthorized access to sensitive browser data (history, saved passwords) through content providers with improper permission enforcement.
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
<= 45.0.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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:U/C:H/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.
-
Identify Firefox for Android installationCheck device applications for 'Firefox for Android' or 'Firefox' (the Android variant). Do not confuse with Firefox Focus or Firefox Desktop.Affected if The installed app is Mozilla Firefox for Android (the vulnerable product)
-
Check Firefox for Android versionNavigate to Firefox for Android > Settings > About Firefox. Compare the displayed version number to 45.0.2. Any version <= 45.0.2 is within the affected range.Affected if Installed Firefox for Android version is 45.0.2 or lower
-
Check Android OS versionNavigate to device Settings > About Phone > Android version. Note the numeric version (e.g., 4.4, 4.3, 4.2).Affected if Android OS version is below 5.0 (e.g., 4.4.x, 4.3.x, 4.2.x)
-
Verify content provider exposureThe vulnerability exists in how Firefox for Android exposes content providers (for history, passwords, bookmarks) with Signature permission checks that can be bypassed. No direct configuration check is available; this is confirmed by the version combination above.Affected if Firefox for Android <= 45.0.2 is installed on Android < 5.0, allowing a malicious local application to access browser data via content providers
A user is affected if Firefox for Android version 45.0.2 or lower is installed on a device running Android version 4.x (below 5.0), enabling a crafted application to bypass signature permissions and read browser history and saved passwords.
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 Firefox for Android to version 46.0 or later on devices running Android 5.0 or higher to remediate this vulnerability.
Fix this in Firefox
Scoped from the published advisory
- Consultation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-2810 — 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-2810 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