CVE-2006-1742: Medium severity Mozilla Firefox vulnerability

Published Apr 14, 2006
·
Updated

The JavaScript engine 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 does not properly handle temporary variables that are not garbage collected, which might allow remote attackers to trigger operations on freed memory and cause memory corruption.

Affected Software

30 affected components
Mozilla Firefox=1.5-beta2
Mozilla Mozilla Suite<=1.7.12
Mozilla Firefox=1.0.2
Mozilla Firefox=1.5-beta1
Mozilla Firefox=1.5
Mozilla Mozilla Suite=1.7.10
Mozilla Firefox=1.0.4
Mozilla Mozilla Suite=1.7.8
Mozilla Thunderbird=1.0
Mozilla Thunderbird=1.0.1
Mozilla Thunderbird=1.5-beta2
Mozilla SeaMonkey=1.0
Mozilla Thunderbird=1.0.2
Mozilla Mozilla Suite=1.7.11
Mozilla Firefox=1.0
Mozilla Thunderbird=1.5
Mozilla Firefox=1.0.1
Mozilla Thunderbird=1.0.4
Mozilla Thunderbird=1.0.3
Mozilla Firefox=1.0.3
Mozilla Thunderbird=1.0.6
Mozilla Thunderbird=1.0.5-beta
Mozilla Mozilla Suite=1.7.7
Mozilla Firefox<=1.0.7
Mozilla Mozilla Suite=1.7.6
Mozilla SeaMonkey<=1.0
Mozilla Thunderbird<=1.0.7
Mozilla Thunderbird=1.0.5
Mozilla Firefox=1.0.5
Mozilla Firefox=1.0.6

Event History

Apr 14, 2006
CVE Published
10:02 AM
CVE Published
via MITRE·02:00 PM
Data Sourced
via MITRE·02:00 PM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2006-1742?

CVE-2006-1742 has a moderate severity rating due to the potential for remote attackers to exploit memory handling issues.

2

How do I fix CVE-2006-1742?

To fix CVE-2006-1742, update your Mozilla Firefox, Thunderbird, or SeaMonkey to the latest patched version.

3

Which software is affected by CVE-2006-1742?

CVE-2006-1742 affects multiple versions of Mozilla Firefox, Thunderbird, Mozilla Suite, and SeaMonkey prior to their respective update releases.

4

What types of attacks can be initiated using CVE-2006-1742?

CVE-2006-1742 could potentially allow attackers to execute arbitrary code or crash the affected application by exploiting unsafe memory operations.

5

Are there any known exploits for CVE-2006-1742?

As of now, there are no publicly known active exploits targeting CVE-2006-1742, but it remains a vulnerability that should be patched promptly.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203