FirefoxWeb browser · Mozilla

CVE-2015-7214

MEDIUM · 5.0 CVSS v2.0 Published 2015-12-16

Fix available

A fix is available. Upgrade to after 42.0 or later.

See remediation →

59/100

Remediation priority · Elevated

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

Mozilla Firefox before 43.0 and Firefox ESR 38.x before 38.5 allow remote attackers to bypass the Same Origin Policy via data: and view-source: URIs.

Technical summary

dbcve analysis · high confidence

Mozilla Firefox before 43.0 and Firefox ESR 38.x before 38.5 contains a Same Origin Policy bypass vulnerability where data: and view-source: URIs can be used to access content from other origins, potentially allowing attackers to steal sensitive data from legitimate websites.

MitigationUpgrade Firefox to version 43.0 or later, or Firefox ESR to 38.5 or later. Alternatively, restrict or disable usage of data: and view-source: URIs through browser policies if upgrading is not immediately feasible.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

FirefoxWeb browser

Affected:= 38.0= 38.0.1= 38.0.5= 38.1.0= 38.1.1= 38.2.0= 38.2.1= 38.3.0= 38.4.0<= 42.0

FedoraOperating system

Affected:= 22= 23

LeapOperating system

Affected:= 42.1

OpensuseOperating system

Affected:= 13.1= 13.2

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Authentication: None
Confidentiality: Partial
Integrity: None
Availability: None

AV:N/AC:L/Au:N/C:P/I:N/A:N

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Identify installed Firefox version

Run 'firefox --version' in terminal, or on Windows check Help > About Firefox, or on macOS run 'firefox -v' or check Firefox > About Firefox from menu

Affected if Version is below 43.0 for standard Firefox, or below 38.5 for ESR releases
Determine if Firefox is an ESR release

Check the version output for 'ESR' designation (e.g., 'Firefox 38.4 ESR') or check package manager output (rpm -qi firefox or dpkg -l firefox)

Affected if Running Firefox ESR version 38.x before 38.5
Confirm non-ESR Firefox version

If not ESR, verify the exact version number from version check output against the affected list: 38.0, 38.0.1, 38.0.5, 38.1.0, 38.1.1, 38.2.0, 38.2.1, 38.3.0, 38.4.0, or any version 38.5 through 42.0

Affected if Version is any Firefox release from 38.0 through 42.0 inclusive
Verify browser is actively processing web content

Confirm the Firefox installation is in active use by checking for recent profile activity or running processes (ps aux | grep firefox or tasklist on Windows)

Affected if The vulnerable browser is actively running and capable of loading data: or view-source: URIs

You are affected if Firefox (standard or ESR) version is below 43.0 (or below 38.5 for ESR) and the browser processes web content that could involve data: or view-source: URIs.

Generated from the published advisory. Verify against your own configuration.

Remediation

From vendor data

Upgrade available Upgrade to a release after 42.0

Interim mitigation

Upgrade Firefox to version 43.0 or later, or Firefox ESR to 38.5 or later. Alternatively, restrict or disable usage of data: and view-source: URIs through browser policies if upgrading is not immediately feasible.

Fix this in Firefox Scoped from the published advisory

Consultation4.0 h
Implementation4.0 h
Testing8.0 h
Review / QA2.0 h

18.0 hours of engineering $3,080

Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,928.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2015-7214 — 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

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-7214 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2015-7214?

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.

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

At a glance

A fix existsUpgrade to after 42.0 or later

Severity 5.0 Medium

Exploit likelihood EPSS, next 30 days 6.1%

Affects: Firefox

Remediation

Need this fixed?

Fix this in Firefox 18 hrs · Moderate

Typical engagement from $3,080

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2015-7214 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References