CVE-2013-1489

Description

Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 10 and Update 11, when running on Windows using Internet Explorer, Firefox, Opera, and Google Chrome, allows remote attackers to bypass the "Very High" security level of the Java Control Panel and execute unsigned Java code without prompting the user via unknown vectors, aka "Issue 53" and the "Java Security Slider" vulnerability.

10.0

CVSS

Severity: Critical

CVSS 2.0 •

EPSS 21.86% Top 5%

Vendor Advisory redhat.com Vendor Advisory marc.info Vendor Advisory marc.info Vendor Advisory oracle.com

Affected: n/a n/a

References

Link	Tags
https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A15906	vdb entry signature
http://seclists.org/fulldisclosure/2013/Jan/241	mailing list
http://www.us-cert.gov/cas/techalerts/TA13-032A.html	third party advisory us government resource
http://www.zdnet.com/java-update-doesnt-prevent-silent-exploits-at-all-7000010422/
http://thenextweb.com/insider/2013/01/28/new-vulnerability-bypasses-oracles-attempt-to-stop-malware-drive-by-downloads-via-java-applets/
http://www.kb.cert.org/vuls/id/858729	third party advisory us government resource
http://www.scmagazine.com.au/News/330453%2Cjava-still-unsafe-new-flaws-discovered.aspx
http://rhn.redhat.com/errata/RHSA-2013-0237.html	vendor advisory
http://marc.info/?l=bugtraq&m=136439120408139&w=2	vendor advisory
http://marc.info/?l=bugtraq&m=136733161405818&w=2	vendor advisory
http://blogs.computerworld.com/malware-and-vulnerabilities/21693/yet-another-java-security-flaw-discovered-number-53
http://www.oracle.com/technetwork/topics/security/javacpufeb2013-1841061.html	vendor advisory
http://www.informationweek.com/security/application-security/java-security-work-remains-bug-hunter-sa/240147150
https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A19171	vdb entry signature

Frequently Asked Questions

What is the severity of CVE-2013-1489?: CVE-2013-1489 has been scored as a critical severity vulnerability.
How to fix CVE-2013-1489?: To fix CVE-2013-1489, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2013-1489 being actively exploited in the wild?: It is possible that CVE-2013-1489 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~22% probability that this vulnerability will be exploited by malicious actors in the next 30 days.