CVE-2014-1530
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 · uneditedThe 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 confidenceA 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.
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< 29.0>= 24.0, < 24.5= 19= 20= 12.04= 12.10= 13.10= 14.04= 7.0= 8.0= 5.0= 6.0= 6.5= 5.0= 6.0= 6.5CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Firefox versionOpen Firefox, click Help > About Firefox, or run 'firefox --version' from command lineAffected if Version is less than 29.0, or between 24.0 and 24.5 (24.0 <= version < 24.5)
-
Check Firefox ESR versionOpen 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
-
Check Thunderbird versionOpen Thunderbird, click Help > About Thunderbird, or run 'thunderbird --version' from command lineAffected if Version is less than 24.5
-
Check SeaMonkey versionOpen SeaMonkey, click Help > About SeaMonkey, or run 'seamonkey --version' from command lineAffected if Version is less than 2.26
-
Check installed Mozilla package on LinuxUse 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.
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 data24.529.0
Apply vendor-supplied security updates to upgrade to Firefox 29.0+, Firefox ESR 24.5+, Thunderbird 24.5+, or SeaMonkey 2.26+ as appropriate.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
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 locallyCheck 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- www.mozilla.org
- bugzilla.mozilla.org
- lists.fedoraproject.org
- lists.fedoraproject.org
- lists.opensuse.org
- lists.opensuse.org
- lists.opensuse.org
- lists.opensuse.org
- lists.opensuse.org
- lists.opensuse.org
- rhn.redhat.com
- rhn.redhat.com
- www.debian.org
- www.debian.org
- www.oracle.com
- www.securityfocus.com
- www.securitytracker.com
- www.securitytracker.com
- www.securitytracker.com
- www.ubuntu.com
- www.ubuntu.com
- security.gentoo.org
- secunia.com
- nvd.nist.gov
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-1530 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