Skip to content
Fencer Intel
critical 9.3

CVE-2014-1555 json

Use-after-free vulnerability in the nsDocLoader::OnProgress function in Mozilla Firefox before 31.0, Firefox ESR 24.x before 24.7, and Thun…

published 12y ago modified 4mo ago also EUVD-2014-1631

cvss
9.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
4.9%
EPSS 4.9% chance of exploitation in 30 days, percentile 92%
public exploits
0
none known

Summary

Use-after-free vulnerability in the nsDocLoader::OnProgress function in Mozilla Firefox before 31.0, Firefox ESR 24.x before 24.7, and Thunderbird before 24.7 allows remote attackers to execute arbitrary code via vectors that trigger a FireOnStateChange event.

Patch / fix

  • firefox Ubuntu 14.04 LTS 31.0+build1-0ubuntu0.14.04.1
  • thunderbird Ubuntu 14.04 LTS 1:31.0+build1-0ubuntu0.14.04.1

ubuntu advisories UBUNTU-CVE-2014-1555

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • thunderbird RHEL 5 PRODUCTIVITY, RHEL 5 24.7.0-1.el5_10
  • thunderbird RHEL 6 24.7.0-1.el6_5
  • firefox RHEL 5 24.7.0-1.el5_10
  • firefox RHEL 6 24.7.0-1.el6_5
  • firefox RHEL 7 24.7.0-1.el7_0
  • xulrunner RHEL 7 24.7.0-1.el7_0

red hat advisories RHSA-2014:0918RHSA-2014:0919

  • firefox-esr openSUSE Tumbleweed 128.5.1-1.1
  • MozillaFirefox openSUSE Tumbleweed 50.1.0-1.1
  • MozillaThunderbird openSUSE Tumbleweed 45.5.1-1.1

opensuse advisories openSUSE-SU-2024:14572-1openSUSE-SU-2024:10071-1openSUSE-SU-2024:10230-1

Is CVE-2014-1555 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2014-1555 updated cvss 5.1

Mozilla: Use-after-free with FireOnStateChange event (MFSA 2014-61)

  • Red Hat Enterprise Linux (v. 5 server) firefox 24.7.0-1.el5_10 Red Hat Enterprise Linux Client (v. 7) firefox 24.7.0-1.el7_0, xulrunner 24.7.0-1.el7_0 Red Hat Enterprise Linux Client Optional (v. 7) firefox 24.7.0-1.el7_0, xulrunner 24.7.0-1.el7_0 Red Hat Enterprise Linux ComputeNode Optional (v. 7) xulrunner 24.7.0-1.el7_0 Red Hat Enterprise Linux Desktop (v. 5 client) firefox 24.7.0-1.el5_10, thunderbird 24.7.0-1.el5_10 Red Hat Enterprise Linux Desktop (v. 6) firefox 24.7.0-1.el6_5, thunderbird 24.7.0-1.el6_5
    +1 more products
    Red Hat Enterprise Linux HPC Node Optional (v. 6) firefox 24.7.0-1.el6_5
    fixed: vendor fix RHSA-2014:0919
  • Red Hat Enterprise Linux Optional Productivity Applications (v. 5 server) thunderbird 24.7.0-1.el5_10
    fixed: vendor fix RHSA-2014:0918
  • Red Hat Enterprise Linux Server (v. 6) firefox 24.7.0-1.el6_5 Red Hat Enterprise Linux Server (v. 7) firefox 24.7.0-1.el7_0, xulrunner 24.7.0-1.el7_0
    fixed: vendor fix RHSA-2014:0919
  • Red Hat Enterprise Linux Server Optional (v. 6) thunderbird 24.7.0-1.el6_5
    fixed: vendor fix RHSA-2014:0918
  • Red Hat Enterprise Linux Server Optional (v. 7) firefox 24.7.0-1.el7_0, xulrunner 24.7.0-1.el7_0 Red Hat Enterprise Linux Workstation (v. 6) firefox 24.7.0-1.el6_5, thunderbird 24.7.0-1.el6_5 Red Hat Enterprise Linux Workstation (v. 7) firefox 24.7.0-1.el7_0, xulrunner 24.7.0-1.el7_0 Red Hat Enterprise Linux Workstation Optional (v. 7) firefox 24.7.0-1.el7_0, xulrunner 24.7.0-1.el7_0
    fixed: vendor fix RHSA-2014:0919

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

4.91% chance of exploitation in the next 30 days, higher than 92% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 9.3 AV:N/AC:M/Au:N/C:C/I:C/A:C

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.