critical
10
Advisory Published
Updated

CVE-2013-0801

First published: Thu May 16 2013(Updated: )

Multiple unspecified vulnerabilities in the browser engine in Mozilla Firefox before 21.0, Firefox ESR 17.x before 17.0.6, Thunderbird before 17.0.6, and Thunderbird ESR 17.x before 17.0.6 allow remote attackers to cause a denial of service (memory corruption and application crash) or possibly execute arbitrary code via unknown vectors.

Credit: security@mozilla.org security@mozilla.org

Affected SoftwareAffected VersionHow to fix
Firefox<=20.0.1
Firefox=19.0
Firefox=19.0.1
Firefox=19.0.2
Firefox=20.0
Firefox=17.0
Firefox=17.0.1
Firefox=17.0.2
Firefox=17.0.3
Firefox=17.0.4
Firefox=17.0.5
Thunderbird<=17.0.5
Thunderbird=17.0
Thunderbird=17.0.1
Thunderbird=17.0.2
Thunderbird=17.0.3
Thunderbird=17.0.4
Mozilla Thunderbird=17.0
Mozilla Thunderbird=17.0.1
Mozilla Thunderbird=17.0.2
Mozilla Thunderbird=17.0.3
Mozilla Thunderbird=17.0.4
Mozilla Thunderbird=17.0.5
Firefox ESR=17.0
Firefox ESR=17.0.1
Firefox ESR=17.0.2
Firefox ESR=17.0.3
Firefox ESR=17.0.4
Firefox ESR=17.0.5

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-2013-0801?

    CVE-2013-0801 has a moderate severity rating as it allows remote attackers to cause denial of service due to memory corruption.

  • How do I fix CVE-2013-0801?

    To fix CVE-2013-0801, update your Mozilla Firefox, Firefox ESR, or Thunderbird to the latest version available.

  • Which versions are affected by CVE-2013-0801?

    CVE-2013-0801 affects Mozilla Firefox versions before 21.0, Firefox ESR 17.x before 17.0.6, and various versions of Thunderbird.

  • Can CVE-2013-0801 lead to remote code execution?

    While CVE-2013-0801 is primarily a denial of service vulnerability, there is potential for it to lead to remote code execution due to memory corruption.

  • Is there a workaround for CVE-2013-0801?

    The best course of action for CVE-2013-0801 is to update to the latest version, as no specific workaround is recommended.

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