Skip to content
Fencer Intel
critical 10.0

CVE-2013-1719 json

Multiple unspecified vulnerabilities in the browser engine in Mozilla Firefox before 24.0, Thunderbird before 24.0, and SeaMonkey before 2.…

published 13y ago modified 4mo ago also EUVD-2013-1746

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

Summary

Multiple unspecified vulnerabilities in the browser engine in Mozilla Firefox before 24.0, Thunderbird before 24.0, and SeaMonkey before 2.21 allow remote attackers to cause a denial of service (memory corruption and application crash) or possibly execute arbitrary code via unknown vectors.

Patch / fix

  • MozillaFirefox openSUSE Tumbleweed 50.1.0-1.1
  • MozillaThunderbird openSUSE Tumbleweed 45.5.1-1.1

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

Is CVE-2013-1719 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-2013-1719 updated cvss 6.8

Mozilla: Miscellaneous memory safety hazards (rv:24.0) (MFSA 2013-76)

  • Red Hat Enterprise Linux 5 firefox, thunderbird Red Hat Enterprise Linux 6 firefox, thunderbird
    not affected: vulnerable code not present

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

5.44% 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 10.0 AV:N/AC:L/Au:N/C:C/I:C/A:C

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

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.