high
7.5
CWE
264
Advisory Published
Updated

CVE-2008-2802

First published: Mon Jul 07 2008(Updated: )

Mozilla Firefox before 2.0.0.15, Thunderbird 2.0.0.14 and earlier, and SeaMonkey before 1.1.10 allow remote attackers to execute arbitrary code via an XUL document that includes a script from a chrome: URI that points to a fastload file, related to this file's "privilege level."

Credit: secalert@redhat.com

Affected SoftwareAffected VersionHow to fix
Firefox=2.0.0.12
Mozilla SeaMonkey<=1.1.9
Thunderbird=2.0.0.4
Mozilla SeaMonkey=1.1.8
Mozilla SeaMonkey=1.1.7
Thunderbird=2.0.0.6
Mozilla SeaMonkey=1.1.3
Firefox=2.0.0.2
Thunderbird=2.0.0.9
Mozilla SeaMonkey=1.1.5
Thunderbird=2.0.0.8
Thunderbird<=2.0.0.14
Firefox=2.0.0.7
Mozilla SeaMonkey=1.1
Firefox=2.0.0.9
Thunderbird=2.0.0.3
Thunderbird=2.0.0.2
Mozilla SeaMonkey=1.1.2
Thunderbird=2.0.0.0
Thunderbird=2.0.0.12
Firefox=2.0
Firefox<=2.0.0.14
Thunderbird=2.0.0.13
Firefox=2.0.0.3
Firefox=2.0.0.6
Mozilla SeaMonkey=1.1.6
Thunderbird=2.0.0.11
Firefox=2.0.0.11
Firefox=2.0.0.4
Firefox=2.0.0.13
Firefox=2.0.0.1
Thunderbird=2.0.0.5
Thunderbird=2.0.0.1
Firefox=2.0.0.8
Firefox=2.0.0.5
Firefox=2.0.0.10
Mozilla SeaMonkey=1.1.4

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2008-2802?

    CVE-2008-2802 is considered critical due to its potential to allow remote attackers to execute arbitrary code.

  • How do I fix CVE-2008-2802?

    To fix CVE-2008-2802, users should update their Mozilla Firefox, Thunderbird, or SeaMonkey to the latest versions provided by Mozilla.

  • Which versions of software are affected by CVE-2008-2802?

    CVE-2008-2802 affects Mozilla Firefox before 2.0.0.15, Thunderbird before 2.0.0.14, and SeaMonkey before 1.1.10.

  • What types of attacks exploit CVE-2008-2802?

    CVE-2008-2802 can be exploited through specially crafted XUL documents that include scripts from compromised chrome: URIs.

  • Is there a workaround for CVE-2008-2802?

    The best practice for handling CVE-2008-2802 is to apply the necessary software updates, as there are no effective workarounds.

Company

Resources

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.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203