CVE-2009-2464: Critical severity firefox vulnerability

Published Jul 22, 2009
·
Updated

The nsXULTemplateQueryProcessorRDF::CheckIsSeparator function in Mozilla Firefox before 3.0.12, SeaMonkey 2.0a1pre, and Thunderbird allows remote attackers to cause a denial of service (memory corruption and application crash) or possibly execute arbitrary code via vectors related to loading multiple RDF files in a XUL tree element.

Affected Software

117 affected components
Mozilla Firefox=0.1
Mozilla Firefox=0.9_rc
Mozilla Firefox=0.8
Mozilla Firefox=2.0.0.12
Mozilla Firefox=1.5-beta2
Mozilla Thunderbird=2.0.0.4
Mozilla Firefox=3.0.7
Mozilla Firefox=1.5.2
Mozilla Thunderbird=2.0.0.6
Mozilla Firefox=3.0.9
Mozilla Firefox=1.5.0.6
Mozilla Firefox=1.8
Mozilla Thunderbird=2.0.0.21
Mozilla Firefox=2.0.0.2
Mozilla Firefox=1.5.0.10
Mozilla Firefox=1.5.0.3
Mozilla SeaMonkey=2.0a1pre
Mozilla Firefox=3.0.8
Mozilla Firefox=1.5.0.11
Mozilla Thunderbird=2.0.0.18
Mozilla Firefox=1.4.1
Mozilla Thunderbird=2.0.0.9
Mozilla Firefox=1.5.4
Mozilla Firefox=1.0.2
Mozilla Thunderbird=2.0.0.15
Mozilla Firefox=3.0.4
Mozilla Firefox=1.5-beta1
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 Firefox=3.0.5
Mozilla Firefox=1.5
Mozilla Firefox=0.9.1
Mozilla Firefox=1.0.4
Mozilla Firefox=2.0.0.7
Mozilla Firefox=1.0.7
Mozilla Firefox=2.0.0.9
Mozilla Firefox=0.10.1
Mozilla Thunderbird=2.0.0.3
Mozilla Firefox=0.9
Mozilla Firefox=2.0.0.16
Mozilla Firefox=3.0-beta2
Mozilla Firefox=1.5.6
Mozilla Thunderbird=2.0.0.2
Mozilla Firefox=2.0.0.17
Mozilla Firefox=0.7
Mozilla Firefox=2.0.0.15
Mozilla Firefox=3.0.10
Mozilla Firefox=0.2
Mozilla Firefox=0.3
Mozilla Thunderbird=2.0.0.0
Mozilla Firefox=1.0
Mozilla Firefox=3.0.3
Mozilla Firefox<=3.0.11
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-beta1
Mozilla Firefox=2.0.0.14
Mozilla Firefox=0.6
Mozilla Thunderbird=2.0.0.13
Mozilla Firefox=0.7.1
Mozilla Firefox=3.0.6
Mozilla Thunderbird=2.0.0.14
Mozilla Firefox=1.5.0.8
Mozilla Firefox=1.0.6
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.7
Mozilla Firefox=1.5.0.12
Mozilla Firefox=2.0.0.6
Mozilla Thunderbird=2.0.0.11
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=0.5
Mozilla Firefox=0.6.1
Mozilla Firefox=1.5.1
Mozilla Firefox=2.0.0.21
Mozilla Firefox=0.9.3
Mozilla Firefox=2.0.0.13
Mozilla Firefox=2.0.0.18
Mozilla Firefox=2.0-rc2
Mozilla Firefox=2.0.0.1
Mozilla Firefox=3.0.2
Mozilla Thunderbird=2.0.0.5
Mozilla Firefox=1.5.5
Mozilla Firefox=0.9.2
Mozilla Firefox=1.0-preview_release
Mozilla Thunderbird=2.0.0.1
Mozilla Firefox=2.0-beta_1
Mozilla Firefox=2.0.0.20
Mozilla Firefox=2.0.0.8
Mozilla Firefox=3.0-beta5
Mozilla Firefox=0.9-rc
Mozilla Firefox=2.0.0.19
Mozilla Firefox=1.5.8
Mozilla Firefox=1.5.3
Mozilla Firefox=0.4
Mozilla Firefox=1.5.0.4
Mozilla Firefox=1.5.0.1
Mozilla Firefox=0.10
Mozilla Firefox=1.0.5
Mozilla Firefox=2.0.0.5
Mozilla Firefox=2.0.0.10
Mozilla Firefox=2.0-rc3
Mozilla Firefox=3.0-alpha
Mozilla Thunderbird=2.0.0.19
Mozilla Firefox=1.0.6
Mozilla Firefox=1.0.8

Event History

Jul 22, 2009
CVE Published
via MITRE·06:00 PM
Data Sourced
via MITRE·06:00 PM
Description

Frequently Asked Questions

1

What is the severity of CVE-2009-2464?

CVE-2009-2464 has a high severity due to potential memory corruption and application crash leading to denial of service or arbitrary code execution.

2

How do I fix CVE-2009-2464?

To fix CVE-2009-2464, users should update their Mozilla Firefox, SeaMonkey, or Thunderbird to the latest version available that has the vulnerability patched.

3

What versions are affected by CVE-2009-2464?

CVE-2009-2464 affects multiple versions including Firefox before 3.0.12, SeaMonkey 2.0a1pre, and Thunderbird before a specific update.

4

Can CVE-2009-2464 be exploited remotely?

Yes, CVE-2009-2464 can be exploited remotely by attackers through specific vectors while loading resources in affected software.

5

Is there a workaround for CVE-2009-2464?

There is no specific workaround for CVE-2009-2464, so the best approach is to update to the latest version of the affected applications.

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