What is CVE-2013-2423?A low-severity flaw criminals are using now.
CVE-2013-2423 is a low-severity flaw (CVSS 3.7) in JRE from Oracle, published on 17 April 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 85%. If you run an affected version, patch it first.
Published 17 April 2013. Record last updated 16 June 2026. We keep this page's data up to date.
What is CVE-2013-2423? In plain terms.
It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can change some data.
Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 17 and earlier, and OpenJDK 7, allows remote attackers to affect integrity via unknown vectors related to HotSpot. NOTE: the previous information is from the April 2013 CPU. Oracle has not commented on claims from the original researcher that this vulnerability allows remote attackers to bypass permission checks by the MethodHandles method and modify arbitrary public final fields using reflection and type confusion, as demonstrated using integer and double fields to disable the security manager.
What kind of flaw is it?
- CWE-284Improper Access Control
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 offHard: conditions must line up
- Login needed firstNo login needed
- Does someone have to clickNo, nobody has to do anything
- What an attacker getsCan change some data
Severity vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
Is CVE-2013-2423 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 85%.
Timeline
- Published
- Record last updated
CVE-2013-2423 scores 74. 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-2423 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-2423? 3 products.
The published record lists 3 products from 3 vendors. If you run one of these, check your version, then go to the fix below.
- Application
JRE
by Oracle
Affected versions1.7.01.7.0-update11.7.0-update21.7.0-update31.7.0-update41.7.0-update51.7.0-update61.7.0-update71.7.0-update91.7.0-update101.7.0-update111.7.0-update131.7.0-update15 - Operating system
Opensuse
by Opensuse
Affected versions12.3 - Operating system
Ubuntu Linux
by Canonical
Affected versions12.10
How do I fix CVE-2013-2423? 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 advisories and patch notes 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
17 links- Jdk7u Dev (opens in a new tab)java.net
- Javacpuapr2013 1928497 (opens in a new tab)oracle.com
- Security Icedtea 2 3 9 for Openjdk 7 Released (opens in a new tab)fuseyism.com · 2013
- Java Is So Confusing (opens in a new tab)spiderlabs.com · 2013
- Msg00099 (opens in a new tab)opensuse.org · 2013
- Errata (opens in a new tab)redhat.com · 2013
Does CVE-2013-2423 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
Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 17 and earlier, and OpenJDK 7, allows remote attackers t...
- Matched to
- JRE 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-2423 is a low-severity flaw in JRE from Oracle, published on 17 April 2013. It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can change some data.
It scores 3.7 out of 10 on the CVSS severity scale, which is low. Our risk score for CVE-2013-2423 is 74 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 85%.
For JRE from Oracle: 1.7.0, 1.7.0-update1, 1.7.0-update2, 1.7.0-update3, 1.7.0-update4, 1.7.0-update5 and 7 more. The record lists 3 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.