FirefoxWeb browser · Mozilla

CVE-2014-1530

MEDIUM · 6.1 CVSS v3.1 Published 2014-04-30
Fix available
A fix is available. Upgrade to 24.5 / 29.0 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 docshell implementation in Mozilla Firefox before 29.0, Firefox ESR 24.x before 24.5, Thunderbird before 24.5, and SeaMonkey before 2.26 allows remote attackers to trigger the loading of a URL with a spoofed baseURI property, and conduct cross-site scripting (XSS) attacks, via a crafted web site that performs history navigation.

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

A vulnerability in the docshell implementation of Mozilla Firefox, Firefox ESR, Thunderbird, and SeaMonkey allows malicious websites to spoof the baseURI property during history navigation, enabling cross-site scripting (XSS) attacks against users.

MitigationApply vendor-supplied security updates to upgrade to Firefox 29.0+, Firefox ESR 24.5+, Thunderbird 24.5+, or SeaMonkey 2.26+ as appropriate.

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:< 29.0>= 24.0, < 24.5
FedoraOperating system
Affected:= 19= 20
Ubuntu LinuxOperating system
Affected:= 12.04= 12.10= 13.10= 14.04
Debian LinuxOperating system
Affected:= 7.0= 8.0
Enterprise Linux DesktopOperating system
Affected:= 5.0= 6.0
Enterprise Linux EusOperating system
Affected:= 6.5
Enterprise Linux ServerOperating system
Affected:= 5.0= 6.0
Enterprise Linux Server AusOperating system
Affected:= 6.5

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
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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. Check Firefox version
    Open Firefox, click Help > About Firefox, or run 'firefox --version' from command line
    Affected if Version is less than 29.0, or between 24.0 and 24.5 (24.0 <= version < 24.5)
  2. Check Firefox ESR version
    Open Firefox ESR, click Help > About Firefox, or check installed package with 'rpm -q firefox-esr' or 'dpkg -l firefox-esr'
    Affected if Version is less than 24.5
  3. Check Thunderbird version
    Open Thunderbird, click Help > About Thunderbird, or run 'thunderbird --version' from command line
    Affected if Version is less than 24.5
  4. Check SeaMonkey version
    Open SeaMonkey, click Help > About SeaMonkey, or run 'seamonkey --version' from command line
    Affected if Version is less than 2.26
  5. Check installed Mozilla package on Linux
    Use package manager: 'rpm -qa | grep -i firefox' (RHEL/Fedora) or 'dpkg -l | grep -i firefox' (Ubuntu/Debian)
    Affected if Package version matches an affected release (Firefox 24.x before 24.5, or versions below 29.0)

A user is affected if they run any Firefox, Firefox ESR, Thunderbird, or SeaMonkey version that falls within the vulnerable ranges: less than 24.5 for ESR/Thunderbird, 24.0-24.4 for Firefox, or less than 29.0 for Firefox.

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 24.5 / 29.0 or later
Fixed in 24.529.0
Interim mitigation

Apply vendor-supplied security updates to upgrade to Firefox 29.0+, Firefox ESR 24.5+, Thunderbird 24.5+, or SeaMonkey 2.26+ as appropriate.

Fix this in Firefox Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-1530 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