A flaw was found in the Networking component of OpenJDK in the way the HTTP/2 protocol implementation cached server connections. This could potentially allow malicious servers connecting from the same IP address to perform a spoofing attack.

It was discovered that the Lightweight HTTP Server component of OpenJDK did not limit the number of connections accepted from HTTP clients. This could result in resource exhaustion if multiple instances of a malicious applications were started at the same time, possibly preventing other applications on the system from being able to communicate over the network.

An unspecified vulnerability in Java SE related to the Security component could allow an unauthenticated attacker to update, insert or delete data resulting in a low integrity impact using unknown attack vectors.

An unspecified vulnerability in Java SE related to the Security component could allow an unauthenticated attacker to update, insert or delete data resulting in a low integrity impact using unknown attack vectors.

A flaw was discovered in the way the Security component of OpenJDK processed X.509 certificates, possibly allowing a specially crafted X.509 certificate to trigger excessive heap memory usage in a Java application processing such certificate.