FirefoxWeb browser · Mozilla
CVE-2012-3979
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 15.0 on Android does not properly implement unspecified callers of the __android_log_print function, which allows remote attackers to execute arbitrary code via a crafted web page that calls the JavaScript dump function.
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 15.0 on Android has an improper implementation of the __android_log_print function when called through the JavaScript dump() function. This allows remote attackers to achieve arbitrary code execution via a crafted web page that triggers this code path.
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
<= 14.0= 0.1= 0.2= 0.3= 0.4= 0.5= 0.6= 0.6.1= 0.7= 0.7.1= 0.8= 0.9
Firefox MobileWeb browser
= 6.0.1= 6.0.2= 10.0= 10.0.1= 10.0.2= 10.0.3= 10.0.4all 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
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 the device runs Google AndroidCheck the device operating system. On Android, go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shell.Affected if The device is not running Android - if so, this specific vulnerability does not apply as it targets the Android-specific __android_log_print implementation.
-
Identify the installed Mozilla Firefox version on AndroidOn the Firefox mobile browser, navigate to Settings > Help > About Firefox, or check the version listed in the device's application manager.Affected if Firefox version is 14.0 or lower, OR matches any of these specific versions: 0.1, 0.2, 0.3, 0.4, 0.5, 0.6, 0.6.1, 0.7, 0.7.1, 0.8, 0.9, 6.0.1, 6.0.2, 10.0, 10.0.1, 10.0.2, 10.0.3, or 10.0.4.
-
Verify the JavaScript dump() function is accessibleOpen a web page in Firefox Android and attempt to execute dump('test') in the JavaScript console (accessible via about:config or a developer console if available). The dump() function writes to the Android system log.Affected if The dump() function executes without errors - this confirms the vulnerable code path is present and could be triggered by malicious web content.
A user is affected if they are running Firefox on an Android device with version below 15.0 (or matching any of the specific affected versions listed) and the dump() function is functional in their browser environment.
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 for Android to version 15.0 or later to obtain the vendor patch for this vulnerability.
Fix this in Firefox
Scoped from the published advisory
- Consultation4.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,488.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-3979 — 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-2012-3979 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