CVE-2013-1692: CSRF

Published Jun 26, 2013
·
Updated

Mozilla Firefox before 22.0, Firefox ESR 17.x before 17.0.7, Thunderbird before 17.0.7, and Thunderbird ESR 17.x before 17.0.7 do not prevent the inclusion of body data in an XMLHttpRequest HEAD request, which makes it easier for remote attackers to conduct cross-site request forgery (CSRF) attacks via a crafted web site.

Affected Software

34 affected components
Mozilla Firefox<=21.0
Mozilla Firefox=19.0
Mozilla Firefox=19.0.1
Mozilla Firefox=19.0.2
Mozilla Firefox=20.0
Mozilla Firefox=20.0.1
Mozilla Firefox=17.0
Mozilla Firefox=17.0.1
Mozilla Firefox=17.0.2
Mozilla Firefox=17.0.3
Mozilla Firefox=17.0.4
Mozilla Firefox=17.0.5
Mozilla Firefox=17.0.6
Mozilla Thunderbird<=17.0.6
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
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 Firefox ESR=17.0
Mozilla Firefox ESR=17.0.1
Mozilla Firefox ESR=17.0.2
Mozilla Firefox ESR=17.0.3
Mozilla Firefox ESR=17.0.4
Mozilla Firefox ESR=17.0.5
Mozilla Firefox ESR=17.0.6

Event History

Jun 26, 2013
CVE Published
via MITRE·01:00 AM
Data Sourced
via MITRE·01:00 AM
Description

Frequently Asked Questions

1

What is the severity of CVE-2013-1692?

CVE-2013-1692 has a moderate severity as it allows for potential cross-site request forgery (CSRF) attacks.

2

How do I fix CVE-2013-1692?

To fix CVE-2013-1692, update affected versions of Mozilla Firefox, Firefox ESR, and Thunderbird to the latest version.

3

Which versions are affected by CVE-2013-1692?

CVE-2013-1692 affects Mozilla Firefox versions before 22.0, Firefox ESR versions before 17.0.7, and Thunderbird versions before 17.0.7.

4

What types of applications are impacted by CVE-2013-1692?

CVE-2013-1692 impacts Mozilla Firefox, Firefox ESR, Thunderbird, and Thunderbird ESR applications.

5

What could be the consequences of CVE-2013-1692?

The consequences of CVE-2013-1692 include the potential for attackers to manipulate user actions through cross-site request forgery attacks.

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