dbcve.org
FirefoxWeb browser · Mozilla

CVE-2014-1501

MEDIUM · 5.8 CVSS v2.0 Published 2014-03-19
Fix available
A fix is available. Upgrade to after 27.0.1 or later.
See remediation →
67/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
Mozilla Firefox before 28.0 on Android allows remote attackers to bypass the Same Origin Policy and access arbitrary file: URLs via vectors involving the "Open Link in New Tab" menu selection.

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

Mozilla Firefox before 28.0 on Android contains a Same Origin Policy bypass vulnerability where the 'Open Link in New Tab' feature can be manipulated to access arbitrary file: URLs, allowing remote attackers to read local files on the device.

MitigationUpgrade Firefox for Android to version 28.0 or later. Implement mobile device management to ensure browsers remain updated.

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:<= 27.0.1= 0.1= 0.2= 0.3= 0.4= 0.5= 0.6= 0.6.1= 0.7= 0.7.1= 0.8= 0.9
SolarisOperating system
Affected:= 11.3
Linux Enterprise DesktopOperating system
Affected:= 11
Linux Enterprise ServerOperating system
Affected:= 11
Linux Enterprise Software Development KitOperating system
Affected:= 11

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
M
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
None

AV:N/AC:M/Au:N/C:P/I:P/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. Identify if Firefox for Android is installed
    On the Android device, go to Settings > Apps > Mozilla Firefox, or run 'adb shell pm list packages | grep mozilla' to list Firefox packages
    Affected if The package org.mozilla.firefox is present on the device
  2. Check Firefox for Android version number
    On the Android device, go to Settings > Apps > Mozilla Firefox > Version, or run 'adb shell dumpsys package org.mozilla.firefox' and look for versionName in the output
    Affected if The version shown is 27.0.1 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
  3. Check Firefox version on Oracle Solaris 11.3
    Run 'firefox --version' or check the bundled Firefox version in /usr/lib/firefox
    Affected if Firefox version on Solaris 11.3 is 27.0.1 or lower
  4. Check Firefox version on SUSE Linux Enterprise 11
    Run 'rpm -q firefox' or 'firefox --version' to query the installed Firefox package version
    Affected if Firefox version is 27.0.1 or lower on SUSE Enterprise Desktop/Server/SDK version 11

You are affected if Firefox (on Android, Oracle Solaris 11.3, or SUSE Linux Enterprise 11) with version 27.0.1 or lower, or any of the specific versions 0.1 through 0.9, is installed and the browser is used to open untrusted web pages.

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 27.0.1
Interim mitigation

Upgrade Firefox for Android to version 28.0 or later. Implement mobile device management to ensure browsers remain updated.

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-1501 — 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-1501 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