What is CVE-2013-1690?A high-severity flaw criminals are using now.
CVE-2013-1690 is a high-severity flaw (CVSS 8.8) in Firefox from Mozilla, published on 26 June 2013. It is on the list of flaws known to be exploited, so criminals are already using it. The latest forecast puts its chance of use in the next 30 days at 69%. If you run an affected version, patch it first.
Published 26 June 2013. Record last updated 22 October 2025. We keep this page's data up to date.
What is CVE-2013-1690? In plain terms.
It can be attacked from anywhere on the internet without logging in, but a person has to take an action first. If it works, the attacker can read data, change data and take it offline.
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 properly handle onreadystatechange events in conjunction with page reloading, which allows remote attackers to cause a denial of service (application crash) or possibly execute arbitrary code via a crafted web site that triggers an attempt to execute data at an unmapped memory location.
What kind of flaw is it?
- CWE-119Improper Restriction of Operations within the Bounds of a Memory Buffer
How an attack on it works
Read straight from its severity rating, translated out of the shorthand.
- Where an attacker can beAnywhere on the internet
- How hard it is to pull offEasy: no special conditions
- Login needed firstNo login needed
- Does someone have to clickYes, a person has to take an action
- What an attacker getsCan read data, change data and take it offline
Severity vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Is CVE-2013-1690 being exploited? Yes.
Attackers are already using it. It is on the government list of flaws known to be exploited, and the latest forecast puts the chance of it being used in the next 30 days at 69%.
Timeline
- Published
- Record last updated
- Exploit likelihood jumped
CVE-2013-1690 scores 76. Action: Emergency patch.
We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:
- Evidence it is being exploitedBiggest factor
- How severe it isStrong factor
- How widely exposed it isSmaller factor
- Threat activity around itSmaller factor
85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.
When CVE-2013-1690 matches software you track, it lands in your list with its score and the reasons behind it.
See your own ranked list →Who is affected by CVE-2013-1690? 15 products.
The published record lists 15 products from 6 vendors. Versions are shown as published: "before 22.0" means every version up to, but not including, 22.0. If you run one of these, check your version, then go to the fix below.
- Application
Firefox
by Mozilla
Affected versionsbefore 22.017.0 to before 17.0.7 - Operating system
Linux Enterprise Server
by Suse
Affected versions10-sp411-sp111-sp211-sp3 - Operating system
Linux Enterprise Desktop
by Suse
Affected versions10-sp411-sp211-sp3 - Operating system
Opensuse
by Opensuse
Affected versions11.412.212.3 - Operating system
Ubuntu Linux
by Canonical
Affected versions12.0412.1013.04 - Operating system
Enterprise Linux Desktop
by Red Hat
Affected versions5.06.0 - Operating system
Enterprise Linux Eus
by Red Hat
Affected versions5.96.4 - Operating system
Enterprise Linux Server
by Red Hat
Affected versions5.06.0 - Operating system
Enterprise Linux Server Aus
by Red Hat
Affected versions5.96.4
How do I fix CVE-2013-1690? Four steps.
- Check whether you run itCompare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
- Apply the vendor’s fixInstall the update named in the vendor’s advisory. We’ve put the advisory first in the list.
- If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
- Check it wasn’t used before you patchedBecause criminals are already using this flaw, look for signs of a break-in on affected systems using the vendor’s guidance.
References
18 linksDoes CVE-2013-1690 affect you? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 flaw being exploited affects software Acme tracks
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 properly handle onready...
- Matched to
- Firefox on Acme's software list
- What to do
- Patch first, then check for signs of use
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
CVE-2013-1690 is a high-severity flaw in Firefox from Mozilla, published on 26 June 2013. It can be attacked from anywhere on the internet without logging in, but a person has to take an action first. If it works, the attacker can read data, change data and take it offline.
It scores 8.8 out of 10 on the CVSS severity scale, which is high. Our risk score for CVE-2013-1690 is 76 out of 100, which is High. Its action is "Emergency patch". Attackers are using this flaw today. If you run an affected version, it goes to the top of your list.
Attackers are already using it. It is on the government list of flaws known to be exploited, and the latest forecast puts the chance of it being used in the next 30 days at 69%.
For Firefox from Mozilla: before 22.0, 17.0 to before 17.0.7. The record lists 15 products in all, each with its versions, under "Who is affected" on this page.
Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet. Because criminals are already using it, also check affected systems for signs of a break-in.