CVE-2006-1737

UnknownEPSS 4.80%

Last modified

CVE-2006-1737 is a vulnerability of currently unknown severity. Integer overflow in Mozilla Firefox and Thunderbird 1.x before 1.5 and 1.0.x before 1.0.8, Mozilla Suite before 1.7.13, and SeaMonkey before 1.0 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary bytecode via JavaScript with a large regular expression.. EPSS estimates a 4.80% chance of exploitation in the next 30 days.

Description

Integer overflow in Mozilla Firefox and Thunderbird 1.x before 1.5 and 1.0.x before 1.0.8, Mozilla Suite before 1.7.13, and SeaMonkey before 1.0 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary bytecode via JavaScript with a large regular expression.

Metrics

EPSS Probability
4.80%

90.8th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
MozillaFirefox1.0
MozillaFirefox1.0.1
MozillaFirefox1.0.2
MozillaFirefox1.0.3
MozillaFirefox1.0.4
MozillaFirefox1.0.5
MozillaFirefox1.0.6
MozillaFirefox1.0.7
MozillaFirefox1.5
MozillaMozilla Suite1.7.6
MozillaMozilla Suite1.7.7
MozillaMozilla Suite1.7.8
MozillaMozilla Suite1.7.10
MozillaMozilla Suite1.7.11
MozillaMozilla Suite1.7.12
MozillaSeamonkey1.0
MozillaThunderbird1.0
MozillaThunderbird1.0.1
MozillaThunderbird1.0.2
MozillaThunderbird1.0.3
MozillaThunderbird1.0.4
MozillaThunderbird1.0.5
MozillaThunderbird1.0.6
MozillaThunderbird1.0.7
MozillaThunderbird1.5

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2006-1737?
Integer overflow in Mozilla Firefox and Thunderbird 1.x before 1.5 and 1.0.x before 1.0.8, Mozilla Suite before 1.7.13, and SeaMonkey before 1.0 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary bytecode via JavaScript with a large regular expression.
How severe is CVE-2006-1737?
Severity scoring for CVE-2006-1737 is pending analysis. The EPSS model estimates a 4.80% probability of exploitation in the next 30 days.
How do I fix CVE-2006-1737?
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.

Are you affected by CVE-2006-1737?

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

Scan your code now

Source: NVD / NIST