critical
10
CWE
20 79
Advisory Published
Updated

CVE-2013-1710: Input Validation

First published: Wed Aug 07 2013(Updated: )

The crypto.generateCRMFRequest function in Mozilla Firefox before 23.0, Firefox ESR 17.x before 17.0.8, Thunderbird before 17.0.8, Thunderbird ESR 17.x before 17.0.8, and SeaMonkey before 2.20 allows remote attackers to execute arbitrary JavaScript code or conduct cross-site scripting (XSS) attacks via vectors related to Certificate Request Message Format (CRMF) request generation.

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

Affected SoftwareAffected VersionHow to fix
Mozilla SeaMonkey<=2.20
Mozilla SeaMonkey=2.0
Mozilla SeaMonkey=2.0-alpha_1
Mozilla SeaMonkey=2.0-alpha_2
Mozilla SeaMonkey=2.0-alpha_3
Mozilla SeaMonkey=2.0-beta_1
Mozilla SeaMonkey=2.0-beta_2
Mozilla SeaMonkey=2.0-rc1
Mozilla SeaMonkey=2.0-rc2
Mozilla SeaMonkey=2.0.1
Mozilla SeaMonkey=2.0.2
Mozilla SeaMonkey=2.0.3
Mozilla SeaMonkey=2.0.4
Mozilla SeaMonkey=2.0.5
Mozilla SeaMonkey=2.0.6
Mozilla SeaMonkey=2.0.7
Mozilla SeaMonkey=2.0.8
Mozilla SeaMonkey=2.0.9
Mozilla SeaMonkey=2.0.10
Mozilla SeaMonkey=2.0.11
Mozilla SeaMonkey=2.0.12
Mozilla SeaMonkey=2.0.13
Mozilla SeaMonkey=2.0.14
Mozilla SeaMonkey=2.1
Mozilla SeaMonkey=2.1-alpha1
Mozilla SeaMonkey=2.1-alpha2
Mozilla SeaMonkey=2.1-alpha3
Mozilla SeaMonkey=2.1-beta1
Mozilla SeaMonkey=2.1-beta2
Mozilla SeaMonkey=2.1-beta3
Mozilla SeaMonkey=2.1-rc1
Mozilla SeaMonkey=2.1-rc2
Mozilla SeaMonkey=2.2
Mozilla SeaMonkey=2.2-beta1
Mozilla SeaMonkey=2.2-beta2
Mozilla SeaMonkey=2.2-beta3
Mozilla SeaMonkey=2.3
Mozilla SeaMonkey=2.3-beta1
Mozilla SeaMonkey=2.3-beta2
Mozilla SeaMonkey=2.3-beta3
Mozilla SeaMonkey=2.3.1
Mozilla SeaMonkey=2.3.2
Mozilla SeaMonkey=2.3.3
Mozilla SeaMonkey=2.4
Mozilla SeaMonkey=2.4-beta1
Mozilla SeaMonkey=2.4-beta2
Mozilla SeaMonkey=2.4-beta3
Mozilla SeaMonkey=2.4.1
Mozilla SeaMonkey=2.5
Mozilla SeaMonkey=2.5-beta1
Mozilla SeaMonkey=2.5-beta2
Mozilla SeaMonkey=2.5-beta3
Mozilla SeaMonkey=2.5-beta4
Mozilla SeaMonkey=2.6
Mozilla SeaMonkey=2.6-beta1
Mozilla SeaMonkey=2.6-beta2
Mozilla SeaMonkey=2.6-beta3
Mozilla SeaMonkey=2.6-beta4
Mozilla SeaMonkey=2.6.1
Mozilla SeaMonkey=2.7
Mozilla SeaMonkey=2.7-beta1
Mozilla SeaMonkey=2.7-beta2
Mozilla SeaMonkey=2.7-beta3
Mozilla SeaMonkey=2.7-beta4
Mozilla SeaMonkey=2.7-beta5
Mozilla SeaMonkey=2.7.1
Mozilla SeaMonkey=2.7.2
Mozilla SeaMonkey=2.8
Mozilla SeaMonkey=2.8-beta1
Mozilla SeaMonkey=2.8-beta2
Mozilla SeaMonkey=2.8-beta3
Mozilla SeaMonkey=2.8-beta4
Mozilla SeaMonkey=2.8-beta5
Mozilla SeaMonkey=2.8-beta6
Mozilla SeaMonkey=2.9
Mozilla SeaMonkey=2.9-beta1
Mozilla SeaMonkey=2.9-beta2
Mozilla SeaMonkey=2.9-beta3
Mozilla SeaMonkey=2.9-beta4
Mozilla SeaMonkey=2.9.1
Mozilla SeaMonkey=2.10
Mozilla SeaMonkey=2.10-beta1
Mozilla SeaMonkey=2.10-beta2
Mozilla SeaMonkey=2.10-beta3
Mozilla SeaMonkey=2.10.1
Mozilla SeaMonkey=2.11
Mozilla SeaMonkey=2.11-beta1
Mozilla SeaMonkey=2.11-beta2
Mozilla SeaMonkey=2.11-beta3
Mozilla SeaMonkey=2.11-beta4
Mozilla SeaMonkey=2.11-beta5
Mozilla SeaMonkey=2.11-beta6
Mozilla SeaMonkey=2.12
Mozilla SeaMonkey=2.12-beta1
Mozilla SeaMonkey=2.12-beta2
Mozilla SeaMonkey=2.12-beta3
Mozilla SeaMonkey=2.12-beta4
Mozilla SeaMonkey=2.12-beta5
Mozilla SeaMonkey=2.12-beta6
Mozilla SeaMonkey=2.12.1
Mozilla SeaMonkey=2.13
Mozilla SeaMonkey=2.13-beta1
Mozilla SeaMonkey=2.13-beta2
Mozilla SeaMonkey=2.13-beta3
Mozilla SeaMonkey=2.13-beta4
Mozilla SeaMonkey=2.13-beta5
Mozilla SeaMonkey=2.13-beta6
Mozilla SeaMonkey=2.13.1
Mozilla SeaMonkey=2.13.2
Mozilla SeaMonkey=2.14
Mozilla SeaMonkey=2.14-beta1
Mozilla SeaMonkey=2.14-beta2
Mozilla SeaMonkey=2.14-beta3
Mozilla SeaMonkey=2.14-beta4
Mozilla SeaMonkey=2.14-beta5
Mozilla SeaMonkey=2.15
Mozilla SeaMonkey=2.15-beta1
Mozilla SeaMonkey=2.15-beta2
Mozilla SeaMonkey=2.15-beta3
Mozilla SeaMonkey=2.15-beta4
Mozilla SeaMonkey=2.15-beta5
Mozilla SeaMonkey=2.15-beta6
Mozilla SeaMonkey=2.15.1
Mozilla SeaMonkey=2.15.2
Mozilla SeaMonkey=2.16
Mozilla SeaMonkey=2.16-beta1
Mozilla SeaMonkey=2.16-beta2
Mozilla SeaMonkey=2.16-beta3
Mozilla SeaMonkey=2.16-beta4
Mozilla SeaMonkey=2.16-beta5
Mozilla SeaMonkey=2.16.1
Mozilla SeaMonkey=2.16.2
Mozilla SeaMonkey=2.17
Mozilla SeaMonkey=2.17-beta1
Mozilla SeaMonkey=2.17-beta2
Mozilla SeaMonkey=2.17-beta3
Mozilla SeaMonkey=2.17-beta4
Mozilla SeaMonkey=2.17.1
Mozilla SeaMonkey=2.18-beta1
Mozilla SeaMonkey=2.18-beta2
Mozilla SeaMonkey=2.18-beta3
Mozilla SeaMonkey=2.18-beta4
Mozilla SeaMonkey=2.19
Mozilla SeaMonkey=2.19-beta1
Mozilla SeaMonkey=2.19-beta2
Mozilla SeaMonkey=2.20-beta1
Mozilla SeaMonkey=2.20-beta2
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
Mozilla Thunderbird=17.0.6
Mozilla Thunderbird=17.0.7
Firefox<=22.0
Firefox=19.0
Firefox=19.0.1
Firefox=19.0.2
Firefox=20.0
Firefox=20.0.1
Firefox=21.0
Thunderbird<=17.0.7
Thunderbird=17.0
Thunderbird=17.0.1
Thunderbird=17.0.2
Thunderbird=17.0.3
Thunderbird=17.0.4
Thunderbird=17.0.5
Thunderbird=17.0.6
Firefox=17.0
Firefox=17.0.1
Firefox=17.0.2
Firefox=17.0.3
Firefox=17.0.4
Firefox=17.0.5
Firefox=17.0.6
Firefox=17.0.7
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
Firefox ESR=17.0.6
Firefox ESR=17.0.7

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-1710?

    CVE-2013-1710 is classified as a critical vulnerability, allowing remote attackers to execute arbitrary JavaScript code.

  • How do I fix CVE-2013-1710?

    To fix CVE-2013-1710, update Mozilla Firefox, Thunderbird, or SeaMonkey to the latest version as specified by the vendor.

  • Which software versions are affected by CVE-2013-1710?

    CVE-2013-1710 affects Mozilla Firefox versions before 23.0, Thunderbird versions before 17.0.8, and SeaMonkey versions before 2.20.

  • What kind of attacks can be conducted using CVE-2013-1710?

    CVE-2013-1710 allows attackers to conduct cross-site scripting (XSS) attacks and execute arbitrary JavaScript code.

  • Is there a workaround for CVE-2013-1710 until I can apply the fix?

    Currently, no official workaround is provided for CVE-2013-1710, and it is strongly recommended to apply the available updates promptly.

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