CVE-2009-0652: Medium severity Mozilla SeaMonkey vulnerability

Published Feb 20, 2009
·
Updated

The Internationalized Domain Names (IDN) blacklist in Mozilla Firefox 3.0.6 and other versions before 3.0.9; Thunderbird before 2.0.0.21; and SeaMonkey before 1.1.15 does not include box-drawing characters, which allows remote attackers to spoof URLs and conduct phishing attacks, as demonstrated by homoglyphs of the / (slash) and ? (question mark) characters in a subdomain of a .cn domain name, a different vulnerability than CVE-2005-0233. NOTE: some third parties claim that 3.0.6 is not affected, but much older versions perhaps are affected.

Affected Software

88 affected components
Mozilla SeaMonkey=1.1.10
Mozilla SeaMonkey=1.0.3
Mozilla Firefox=2.0.0.12
Mozilla Thunderbird=2.0.0.4
Mozilla SeaMonkey=1.1.8
Mozilla SeaMonkey=1.0.1
Mozilla SeaMonkey=1.1.7
Mozilla Thunderbird=2.0.0.6
Mozilla SeaMonkey=1.0.6
Mozilla Firefox=1.5.0.6
Mozilla SeaMonkey=1.0.9
Mozilla SeaMonkey<=1.1.14
Mozilla SeaMonkey=1.1.3
Mozilla Firefox=2.0.0.2
Mozilla Firefox=1.5.0.10
Mozilla Firefox=1.5.0.3
Mozilla SeaMonkey=1.0
Mozilla Firefox=1.5.0.11
Mozilla Thunderbird=2.0.0.18
Mozilla Thunderbird=2.0.0.9
Mozilla SeaMonkey=1.1.5
Mozilla SeaMonkey=1.0.7
Mozilla Firefox=1.0.2
Mozilla Firefox=3.0.4
Mozilla SeaMonkey=1.1-alpha
Mozilla Thunderbird=2.0.0.16
Mozilla Firefox=3.0.5
Mozilla Firefox=1.5
Mozilla Firefox=1.0.4
Mozilla Firefox=2.0.0.7
Mozilla Firefox=1.0.7
Mozilla SeaMonkey=1.1.12
Mozilla SeaMonkey=1.1
Mozilla Firefox=2.0.0.9
Mozilla Firefox=2.0.0.16
Mozilla Thunderbird<=2.0.0.20
Mozilla Firefox=2.0.0.17
Mozilla SeaMonkey=1.1.2
Mozilla Firefox=2.0.0.15
Mozilla SeaMonkey=1.0.2
Mozilla SeaMonkey=1.0.8
Mozilla Thunderbird=2.0.0.0
Mozilla SeaMonkey=1.1.11
Mozilla Firefox=1.0
Mozilla Firefox=3.0.3
Mozilla SeaMonkey=1.1-beta
Mozilla SeaMonkey=1.1.1
Mozilla Firefox=1.5.0.7
Mozilla Thunderbird=2.0.0.12
Mozilla Firefox=2.0
Mozilla Firefox=1.0.1
Mozilla Firefox=2.0.0.14
Mozilla SeaMonkey=1.0.5
Mozilla Thunderbird=2.0.0.14
Mozilla Firefox=1.5.0.8
Mozilla Firefox=2.0.0.3
Mozilla Firefox=1.5.0.9
Mozilla Thunderbird=2.0.0.17
Mozilla Firefox=1.5.0.5
Mozilla Firefox=1.5.0.12
Mozilla Firefox=2.0.0.6
Mozilla SeaMonkey=1.1.6
Mozilla Firefox=3.0
Mozilla Firefox=2.0.0.11
Mozilla Firefox=1.5.0.2
Mozilla Firefox=1.0.3
Mozilla Firefox=3.0.1
Mozilla Firefox=2.0.0.4
Mozilla Firefox=2.0.0.13
Mozilla Firefox=2.0.0.18
Mozilla Firefox<=3.0.6
Mozilla Firefox=2.0.0.1
Mozilla Firefox=3.0.2
Mozilla Thunderbird=2.0.0.5
Mozilla SeaMonkey=1.1.9
Mozilla SeaMonkey=1.1.13
Mozilla Firefox=2.0.0.20
Mozilla Firefox=2.0.0.8
Mozilla Firefox=2.0.0.19
Mozilla Firefox=1.5.0.4
Mozilla Firefox=1.5.0.1
Mozilla Firefox=1.0.5
Mozilla Firefox=2.0.0.5
Mozilla Firefox=2.0.0.10
Mozilla Thunderbird=2.0.0.19
Mozilla Firefox=1.0.6
Mozilla SeaMonkey=1.1.4
Mozilla Firefox=1.0.8

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Mozilla Firefox to a version that resolves this vulnerability.

    Fixed in 3.0.9
  2. Upgrade

    Upgrade Thunderbird to a version that resolves this vulnerability.

    Fixed in 2.0.0.21
  3. Upgrade

    Upgrade Mozilla SeaMonkey to a version that resolves this vulnerability.

    Fixed in 1.1.15

Event History

Feb 20, 2009
CVE Published
via MITRE·07:00 PM
Data Sourced
via MITRE·07:00 PM
Description
Data Sourced
via NVD·07:30 PM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2009-0652?

CVE-2009-0652 has a medium severity rating due to its potential for phishing attacks through URL spoofing.

2

How do I fix CVE-2009-0652?

To fix CVE-2009-0652, upgrade to a version of Mozilla Firefox that is 3.0.9 or later, Thunderbird 2.0.0.21 or later, or SeaMonkey 1.1.15 or later.

3

Who is affected by CVE-2009-0652?

CVE-2009-0652 affects users of Mozilla Firefox versions prior to 3.0.9, Thunderbird versions before 2.0.0.21, and SeaMonkey versions prior to 1.1.15.

4

What kind of attacks can CVE-2009-0652 allow?

CVE-2009-0652 allows remote attackers to conduct phishing attacks by spoofing URLs using non-standard characters.

5

Is there a workaround for CVE-2009-0652?

While upgrading to a secure version is the best fix, users can also avoid clicking on links from untrusted sources to mitigate risks associated with CVE-2009-0652.

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