It was discovered that the Inet6Address class contained errors when processing IPv6 addresses. This could lead to inaccurate results when processing IPv6 addresses, for example during serialization.
A denial of service flaw was found in the way the JRE processes XML. A remote attacker could use this flaw to supply crafted XML that would lead to a denial of service.
It was discovered that AWT JTable did not properly perform certain access checks. An untrusted Java application or applet could possibly use this flaw to bypass Java sandbox restrictions.
It was discovered that java.util.TimeZone does not properly restrict changing the time zone to the default time zone. An untrusted Java application or applet could exploit this to change the default time zone of their application contexts.
It was discovered that javac did not properly ignore certain ignorable characters. An attacker could influence the integrity and confidentiality of a system by providing specially crafted input, which is then used by javadoc to generate API documentation.
Upstream reports that this issue is relevant to uses where javadoc is used to generate documentation for an untrusted source code and have it hosted on a domain not controlled by the author of the source code (the attacker).
Oracle Java SE Update 45 fixes an unspecified vulnerability in the 2D component (CVE-2013-5801). Upstream has CVSSv2 scored this issue as: 5.0/AV:N/AC:L/Au:N/C:P/I:N/A:N
External Reference:
http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html
It was discovered that AWT component's native ImagingLib failed to properly check image boundaries when preforming image conversion. An untrusted Java application or applet could possibly use this flaw to bypass certain Java sandbox restrictions by reading portions of the JVM memory.
It was discovered that getDeclaringClass() method implementation did not perform class loader package access checks. In certain configurations, an untrusted Java application or applet could possibly use this flaw to bypass certain Java sandbox restrictions.
It was discovered that various OpenJDK classes that represent cryptographic keys could leak private key information by including sensitive data in strings returned by toString() methods. If a Java application called the toString() method on any of the affected classes, it could possibly lead to an unexpected exposure of sensitive key data.
It was discovered that DataFlavor class in the AWT component of OpenJDK failed to perform security checks properly. An untrusted Java application or applet could possibly use this flaw to bypass certain Java sandbox restrictions because of insufficient checks of package access restrictions, or class loader access permission.
http://docs.oracle.com/javase/7/docs/api/java/awt/datatransfer/DataFlavor.html
It was discovered that the Beans component of OpenJDK failed to perform security checks properly. An untrusted Java application or applet could possibly use this flaw to bypass certain Java sandbox restrictions because of insufficient checks of access level modifiers or package access restrictions.
Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 5.0 Update 45 and earlier allows local users to affect confidentiality, integrity, and availability via unknown vectors related to the Java installer.
It was discovered that the ObjectOutputStream class did not properly perform certain access checks when handling subclasses. An untrusted Java application or applet could possibly use this flaw to disclose potentially sensitive information.
It was discovered that the ObjectStreamClass class did not properly protect against circular references. An untrusted Java application or applet could possibly use this flaw to cause a denial of service.
It was discovered that the Networking component did not properly prevent the local address from being revealed. An untrusted Java application or applet could possibly use this flaw to disclose the local address.
It was discovered that access checks for getEnclosingClass, getEnclosingMethod and getEnclosingConstructor were not performed properly. An untrusted Java application or applet could possibly use this flaw to disclose potentially sensitive information.
It was discovered that the java.rmi.dgc.VMID class did not create entirely unique and unpredictable IDs. An untrusted Java application or applet could possibly use this flaw to disclose potentially sensitive information.
Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 21 and earlier, 6 Update 45 and earlier, and 5.0 Update 45 and earlier, and OpenJDK 7, allows remote attackers to affect confidentiality via unknown vectors related to Libraries, a different vulnerability than CVE-2013-2452 and CVE-2013-2455. NOTE: the previous information is from the June 2013 CPU. Oracle has not commented on claims from another vendor that this issue is due to an incorrect "checking order" within the AccessControlContext class.
It was discovered that the JMX component did not properly implement certain class checks. An untrusted Java application or applet could possibly use this flaw to bypass intended class restrictions.
It was discovered that CORBA output streams did not properly implement access restrictions. An untrusted Java application or applet could possibly use this flaw to disclose potentially sensitive information.
It was discovered that the AWT component did not properly manage and restrict certain resources related to the processing of fonts. An untrusted Java application or applet could possibly use this flaw to exhaust available resources and cause a denial of service.
The SerialJavaObject class of the JDBC component did not properly restrict access to certain class packages. An untrusted Java application or applet could possibly use this flaw to bypass Java sandbox restrictions.
It was found that documentation generated by javadoc was vulnerable to a frame injection attack. If such documentation was accessible over a network, and a remote attacker could trick a user into visiting a specially-crafted URL, it would lead to arbitrary web script execution in the context of the user's session if permitted by the browser. It could also be used to perform a phishing attack, by providing frame content that spoofed a login form on the site hosting the vulnerable documentation.
Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 17 and earlier, 6 Update 43 and earlier, 5.0 Update 41 and earlier, and JavaFX 2.2.7 and earlier allows local users to affect confidentiality, integrity, and availability via unknown vectors related to Install.
It was discovered that the Network component did not properly perform InetAddress serialization. An untrusted Java application or applet could possibly use this flaw to disclose sensitive information.
It was discovered that the 2D component did not properly process certain fonts. An untrusted Java application or applet could possibly use this flaw to crash the Java VM.
MBeanInstantiator class implementation in OpenJDK JMX component did not properly check class access before creating new instances. Untrusted Java application or applet could use this flaw to create instances of non-public classes.
It was discovered that InetSocketAddress class did not properly implement serialization. An untrusted Java application or applet could use this flaw to for example deserialize invalid InetSockAddress data without throwing expected exception when encountering invalid data.
External Reference:
http://www.oracle.com/technetwork/topics/security/javacpufeb2013-1841061.html
Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 through Update 11, 6 through Update 38, and 5.0 through Update 38 allows remote attackers to affect confidentiality via vectors related to JMX.
Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 through Update 11, 6 through Update 38, 5.0 through Update 38, and 1.4.240 and earlier, and OpenJDK 6 and 7, allows remote attackers to affect confidentiality via vectors related to JAXP. NOTE: the previous information is from the February 2013 CPU. Oracle has not commented on claims from another vendor that this issue is related to the public declaration of the loadPropertyFile method in the JAXP FuncSystemProperty class, which allows remote attackers to obtain sensitive information.