Strix
26.1K

CVE-2013-5596

UnknownEPSS 3.14%

Last modified

CVE-2013-5596 is a vulnerability of currently unknown severity. The cycle collection (CC) implementation in Mozilla Firefox before 25.0, Firefox ESR 24.x before 24.1, Thunderbird before 24.1, and SeaMonkey before 2.22 does not properly determine the thread for release of an image object, which allows remote attackers to execute arbitrary code or cause a denial of service (race condition and application crash) via a large HTML document containing IMG elements, as demonstrated by the Never-Ending Reddit on reddit.com.. EPSS estimates a 3.14% chance of exploitation in the next 30 days.

Description

The cycle collection (CC) implementation in Mozilla Firefox before 25.0, Firefox ESR 24.x before 24.1, Thunderbird before 24.1, and SeaMonkey before 2.22 does not properly determine the thread for release of an image object, which allows remote attackers to execute arbitrary code or cause a denial of service (race condition and application crash) via a large HTML document containing IMG elements, as demonstrated by the Never-Ending Reddit on reddit.com.

Metrics

EPSS Probability
3.14%

86.3th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersionsUpdate
MozillaThunderbird<= 24.0.1—
MozillaThunderbird17.0—
MozillaThunderbird17.0.1—
MozillaThunderbird17.0.2—
MozillaThunderbird17.0.3—
MozillaThunderbird17.0.4—
MozillaThunderbird17.0.5—
MozillaThunderbird17.0.6—
MozillaThunderbird17.0.7—
MozillaThunderbird17.0.8—
MozillaThunderbird24.0—
MozillaThunderbird Esr17.0.9—
MozillaFirefox24.0—
MozillaFirefox24.0.1—
MozillaFirefox24.0.2—
MozillaFirefox<= 24.0—
MozillaFirefox19.0—
MozillaFirefox19.0.1—
MozillaFirefox19.0.2—
MozillaFirefox20.0—
MozillaFirefox20.0.1—
MozillaFirefox21.0—
MozillaFirefox22.0—
MozillaFirefox23.0—
MozillaFirefox23.0.1—
MozillaSeamonkey<= 2.22Beta2
MozillaSeamonkey2.0—
MozillaSeamonkey2.0.1—
MozillaSeamonkey2.0.2—
MozillaSeamonkey2.0.3—
MozillaSeamonkey2.0.4—
MozillaSeamonkey2.0.5—
MozillaSeamonkey2.0.6—
MozillaSeamonkey2.0.7—
MozillaSeamonkey2.0.8—
MozillaSeamonkey2.0.9—
MozillaSeamonkey2.0.10—
MozillaSeamonkey2.0.11—
MozillaSeamonkey2.0.12—
MozillaSeamonkey2.0.13—
MozillaSeamonkey2.0.14—
MozillaSeamonkey2.1—
MozillaSeamonkey2.10—
MozillaSeamonkey2.10.1—
MozillaSeamonkey2.11—
MozillaSeamonkey2.12—
MozillaSeamonkey2.12.1—
MozillaSeamonkey2.13—
MozillaSeamonkey2.13.1—
MozillaSeamonkey2.13.2—

Showing 50 of 64 affected configurations. See NVD for the full list.

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2013-5596?
The cycle collection (CC) implementation in Mozilla Firefox before 25.0, Firefox ESR 24.x before 24.1, Thunderbird before 24.1, and SeaMonkey before 2.22 does not properly determine the thread for release of an image object, which allows remote attackers to execute arbitrary code or cause a denial of service (race condition and application crash) via a large HTML document containing IMG elements, as demonstrated by the Never-Ending Reddit on reddit.com.
How severe is CVE-2013-5596?
Severity scoring for CVE-2013-5596 is pending analysis. The EPSS model estimates a 3.14% probability of exploitation in the next 30 days.
How do I fix CVE-2013-5596?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2013

View all 2013CVEs →

Are you affected by CVE-2013-5596?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST