dbcve.org
FirefoxWeb browser · Mozilla

CVE-2014-1485

HIGH · 7.5 CVSS v2.0 Published 2014-02-06
Fix available
A fix is available. Upgrade to 2.24 / 27.0 or later.
See remediation →
84/100
Remediation priority · High
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
The Content Security Policy (CSP) implementation in Mozilla Firefox before 27.0 and SeaMonkey before 2.24 operates on XSLT stylesheets according to style-src directives instead of script-src directives, which might allow remote attackers to execute arbitrary XSLT code by leveraging insufficient style-src restrictions.

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

The Content Security Policy implementation in Firefox before 27.0 and SeaMonkey before 2.24 incorrectly applied style-src directives to XSLT stylesheets instead of script-src directives. Since XSLT stylesheets can contain executable code, this allowed attackers to potentially execute arbitrary XSLT code through insufficient style-src restrictions.

MitigationUpgrade to Firefox 27.0 or later, SeaMonkey 2.24 or later, or apply vendor-supplied patches. If immediate patching is not feasible, consider restricting or disabling XSLT processing for untrusted content at the network perimeter.

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
Ubuntu LinuxOperating system
Affected:= 12.04= 12.10= 13.10
SeamonkeyApplication
Affected:< 2.24
SolarisOperating system
Affected:= 11.3
OpensuseOperating system
Affected:= 11.4= 12.3= 13.1
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
Low
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/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 checks

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

  1. Identify the installed browser product and version
    For Firefox: check 'Help' > 'About Firefox' or run 'firefox --version' in terminal. For SeaMonkey: check 'Help' > 'About SeaMonkey' or run 'seamonkey --version'. On Ubuntu/SUSE/Solaris: use package manager like 'dpkg -l firefox' or 'rpm -q firefox'
    Affected if Version is Firefox < 27.0 or SeaMonkey < 2.24
  2. Confirm Content Security Policy is in use
    Inspect HTTP headers for 'Content-Security-Policy' or '<meta http-equiv="Content-Security-Policy" ...>' tags in web pages. Look specifically for 'style-src' directives defined in the policy
    Affected if CSP policy exists with style-src directives defined
  3. Determine if XSLT stylesheets are being loaded
    Review web application code and server responses for XSLT stylesheet references (<?xml-stylesheet type="text/xsl" ...> or similar). Check network traffic or server logs for .xsl/.xslt file requests
    Affected if The browser loads or processes XSLT stylesheets from any source

You are affected if you run Firefox < 27.0 or SeaMonkey < 2.24, use Content Security Policy with style-src directives, and load XSLT stylesheets - the vulnerability allows XSLT code execution through bypassed script-src restrictions.

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 2.24 / 27.0 or later
Fixed in 2.2427.0
Interim mitigation

Upgrade to Firefox 27.0 or later, SeaMonkey 2.24 or later, or apply vendor-supplied patches. If immediate patching is not feasible, consider restricting or disabling XSLT processing for untrusted content at the network perimeter.

Fix this in Firefox Scoped from the published advisory
  • Consultation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
3.0 hours of engineering $750
Get the upgrade done

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 locally
dbcve dependency scanner

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