CVE-2009-2210: Critical severity mozilla seamonkey vulnerability

Published Jun 25, 2009
·
Updated

Mozilla Thunderbird before 2.0.0.22 and SeaMonkey before 1.1.17 allow remote attackers to cause a denial of service (application crash) or possibly execute arbitrary code via a multipart/alternative e-mail message containing a text/enhanced part that triggers access to an incorrect object type.

Affected Software

108 affected components
Mozilla SeaMonkey=1.1.10
Mozilla Thunderbird=1.5.0.7
Mozilla Thunderbird=0.6
Mozilla SeaMonkey=1.0.3
Mozilla Thunderbird=0.7.2
Mozilla Thunderbird=2.0.0.4
Mozilla SeaMonkey=1.1.8
Mozilla SeaMonkey<=1.1.16
Mozilla Thunderbird<=2.0.0.21
Mozilla SeaMonkey=1.0.1
Mozilla SeaMonkey=1.1.7
Mozilla SeaMonkey=1.5.0.10
Mozilla Thunderbird=2.0.0.6
Mozilla SeaMonkey=1.0.6
Mozilla SeaMonkey=1.0.9
Mozilla Thunderbird=0.3
Mozilla SeaMonkey=1.1.3
Mozilla Thunderbird=0.2
Mozilla SeaMonkey=1.0
Mozilla Thunderbird=2.0_.5
Mozilla Thunderbird=1.0.7
Mozilla Thunderbird=2.0.0.18
Mozilla SeaMonkey=1.0.99
Mozilla Thunderbird=2.0.0.9
Mozilla SeaMonkey=1.1.5
Mozilla SeaMonkey=1.0.7
Mozilla SeaMonkey=1.0-beta
Mozilla Thunderbird=2.0_.12
Mozilla Thunderbird=2.0.0.15
Mozilla SeaMonkey=1.1-alpha
Mozilla Thunderbird=2.0.0.16
Mozilla Thunderbird=2.0.0.20
Mozilla Thunderbird=2.0.0.8
Mozilla Thunderbird=2.0.0.7
Mozilla SeaMonkey=1.0-alpha
Mozilla Thunderbird=1.7.1
Mozilla Thunderbird=2.0_8
Mozilla Thunderbird=1.5.0.3
Mozilla Thunderbird=1.5.0.10
Mozilla Thunderbird=1.5.0.5
Mozilla Thunderbird=1.5.0.6
Mozilla SeaMonkey=1.1.12
Mozilla SeaMonkey=1.1
Mozilla Thunderbird=1.0
Mozilla Thunderbird=2.0.0.3
Mozilla Thunderbird=1.0.1
Mozilla SeaMonkey=1.1.14
Mozilla Thunderbird=1.5-beta2
Mozilla Thunderbird=2.0.0.2
Mozilla SeaMonkey=1.1.2
Mozilla SeaMonkey=1.0.2
Mozilla SeaMonkey=1.0.8
Mozilla Thunderbird=1.0.2
Mozilla Thunderbird=2.0.0.0
Mozilla Thunderbird=1.5.0.13
Mozilla SeaMonkey=1.1.11
Mozilla SeaMonkey=1.5.0.9
Mozilla SeaMonkey=1.1-beta
Mozilla SeaMonkey=1.1.1
Mozilla Thunderbird=2.0.0.12
Mozilla Thunderbird=1.5
Mozilla SeaMonkey=1.5.0.8
Mozilla Thunderbird=1.5.0.2
Mozilla SeaMonkey=1.1.5-1.1.10
Mozilla Thunderbird=2.0.0.13
Mozilla SeaMonkey=1.0.5
Mozilla SeaMonkey=1.1.15
Mozilla Thunderbird=2.0_.9
Mozilla Thunderbird=1.5.0.8
Mozilla Thunderbird=2.0.0.14
Mozilla Thunderbird=0.5
Mozilla Thunderbird=1.0.4
Mozilla Thunderbird=1.5.2
Mozilla Thunderbird=2.0.0.17
Mozilla Thunderbird=1.5.0.9
Mozilla Thunderbird=1.5.0.11
Mozilla Thunderbird=0.9
Mozilla Thunderbird=1.0.3
Mozilla SeaMonkey=1.1.6
Mozilla Thunderbird=2.0.0.11
Mozilla Thunderbird=1.5.0.12
Mozilla Thunderbird=2.0_.13
Mozilla Thunderbird=2.0_.14
Mozilla Thunderbird=0.7.3
Mozilla Thunderbird=0.4
Mozilla SeaMonkey=1.0
Mozilla Thunderbird=1.5.1
Mozilla Thunderbird=0.7
Mozilla Thunderbird=1.5.0.14
Mozilla Thunderbird=1.0.6
Mozilla Thunderbird=1.0.5-beta
Mozilla Thunderbird=2.0.0.5
Mozilla Thunderbird=1.7.3
Mozilla SeaMonkey=1.0.4
Mozilla Thunderbird=2.0.0.1
Mozilla SeaMonkey=1.1.9
Mozilla SeaMonkey=1.1.13
Mozilla Thunderbird=1.5.0.1
Mozilla Thunderbird=2.0_.4
Mozilla Thunderbird=1.0.8
Mozilla Thunderbird=0.1
Mozilla Thunderbird=0.7.1
Mozilla Thunderbird=1.0.5
Mozilla Thunderbird=0.8
Mozilla Thunderbird=2.0_.6
Mozilla Thunderbird=2.0.0.19
Mozilla Thunderbird=1.5.0.4
Mozilla SeaMonkey=1.1.4

Event History

Jun 25, 2009
CVE Published
via MITRE·05:00 PM
Data Sourced
via MITRE·05:00 PM
Description

Frequently Asked Questions

1

What is the severity of CVE-2009-2210?

CVE-2009-2210 has a severity rating of moderate, as it can cause denial of service and potentially allow arbitrary code execution.

2

How do I fix CVE-2009-2210?

To fix CVE-2009-2210, upgrade to Mozilla Thunderbird version 2.0.0.22 or later, or SeaMonkey version 1.1.17 or later.

3

What versions of software are affected by CVE-2009-2210?

CVE-2009-2210 affects Mozilla Thunderbird versions prior to 2.0.0.22 and SeaMonkey versions prior to 1.1.17.

4

What type of vulnerability is CVE-2009-2210?

CVE-2009-2210 is a vulnerability that can cause application crashes and potentially execute arbitrary code through malformed email messages.

5

Is there a known exploit for CVE-2009-2210?

Yes, CVE-2009-2210 can be exploited by sending a specially crafted multipart/alternative email message that triggers access to an incorrect object type.

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