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 discovered in the com.sun.org.apache.xml.internal.security.utils.UnsyncByteArrayOutputStream class. A remote attacker could use this flaw to supply crafted XML that would lead to a denial of service.
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 Deployment component (CVE-2013-5812). Upstream has CVSSv2 scored this issue as: 6.4/AV:N/AC:L/Au:N/C:P/I:N/A:P
External Reference:
http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html
Oracle Java SE Update 45 fixes an unspecified vulnerability in the Deployment component (CVE-2013-5831). Upstream has CVSSv2 scored this issue as: 5.0/AV:N/AC:L/Au:N/C:N/I:P/A:N
External Reference:
http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html
Oracle Java SE Update 45 fixes an unspecified vulnerability in the Deployment component (CVE-2013-5819). Upstream has CVSSv2 scored this issue as: 5.0/AV:N/AC:L/Au:N/C:N/I:P/A:N
External Reference:
http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html
Oracle Java SE Update 45 fixes an unspecified vulnerability in the Deployment component (CVE-2013-5818). Upstream has CVSSv2 scored this issue as: 5.0/AV:N/AC:L/Au:N/C:N/I:P/A:N
External Reference:
http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html
Oracle Java SE Update 45 fixes an unspecified vulnerability in the Deployment component (CVE-2013-5776). Upstream has CVSSv2 scored this issue as: 5.0/AV:N/AC:L/Au:N/C:N/I:P/A:N
External Reference:
http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html
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 the JAXWS 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 when invoking object methods, or because of insufficient object type checks.
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.
It was discovered that InterfaceImplementor class in the Scripting 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 interface access level modifiers, package restrictions, or instance class loader.
The fix also marks the com.sun.script. package restricted by adding it to the package.access properly list in the java.security file.
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.
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, and OpenJDK 6 and 7, allows remote attackers to affect integrity via unknown vectors related to Libraries. NOTE: the previous information is from the February 2013 CPU. Oracle has not commented on claims from another vendor that this issue allows remote attackers to interrupt certain threads that should not be interrupted.
Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 through Update 11 and 6 through Update 38, and OpenJDK 6 and 7, allows remote attackers to affect confidentiality via vectors related to JAX-WS. 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 improper restriction of com.sun.xml.internal packages and "Better handling of UI elements."
It was discovered that JSSE component in OpenJDK did not properly validate Diffie-Hellman public keys. A malicious SSL/TLS client could use this flaw to perform a small subgroup attack on the Diffie-Hellman protocol, resulting in weak session key to be negotiated for the connection, or possibly disclose portions of the server's Diffie-Hellman private key.
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, 5.0 through Update 38, and 1.4.240 and earlier, and OpenJDK 6 and 7, allows remote attackers to affect confidentiality and integrity via vectors related to AWT. 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 "insufficient clipboard access premission checks."
Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 through Update 11 and 6 through Update 38, allows local users to affect confidentiality, integrity, and availability via unknown vectors related to the installation process of the client.
Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 through Update 11 and 6 through Update 38 allows remote attackers to affect confidentiality via unknown vectors related to Deployment.
An XSS flaw was discovered in the sun.rmi.transport.proxy CGIHandler class. When error was detected in the request query parameters, an untrusted user input was used in an error string without further sanitization.
External Reference:
http://www.oracle.com/technetwork/topics/security/javacpufeb2013-1841061.html
A flaw was discovered in the SSL/TLS in JSSE component of OpenJDK, that allows malicious clients to make an SSL/TLS server use an excessive amount of CPU time by repeatedly sending ClientHello packets. Client can send pre-generated packet, causing the server to repeatedly perform expensive computations when generating ServerHello response.
This flaw is similar to OpenSSL CVE-2011-4619 (bug #771780), but the problem does not seem to be caused by an attempt to support server gated cryptography (SGC) and rather seems to be caused by an incorrect enforcing of the packet order during the SSL/TLS protocol handshake.
Note that the attacker needs to keep connection open and keep re-sending ClientHello packets to keep server busy.