This month's featured post is on CVE-2018-10237
Java serialization issues have been around for years, but haven’t really garnered much attention until recently when it became clear that attackers could use vulnerable classes to perform deserialization on untrusted data. This Guava component is no exception.
Click on the CVE number in the list below to learn more about this vulnerability, and what you can do if you're using this component in your code.
Unbounded Memory Allocation/Denial of Service attack
Java serialization issues have been around for years, but haven’t really garnered much attention until recently when it became clear that attackers could use vulnerable classes to perform deserialization on untrusted data. Particularly, if the deserialization occurs pre-authentication. Java's type check will ensure you only get valid object trees by strictly validating the expected type. Unfortunately, by the time the type checking completes, compromised platform code could be created and execute significant logic.
By tampering with the request and supplying a request for an abnormally large amount of server memory, the request could overwhelm the server and lead to a denial of service.
Google Guava 11.0 through 24.x before 24.1.1.
Set a limit on the size of the object graph that servers will accept. For Java, narrow the classes that can be deserialized from “any class available” to an application, down to a context-appropriate set of classes.
Apache Tomcat is vulnerable to Information Disclosure, as it sends the response of a "send file" request (request "A") in response to another request (request "B") that is in the pipeline when the processing of the previous request is completed. An attacker can exploit this vulnerability by sending a request to the targeted system while other requests are being processed. This could allow the attacker to gain sensitive information due to the incorrect response sent when processing of a previous request has completed.
org.apache.tomcat: tomcat-coyote, coyote
org.jboss.web: jbossweb jboss.web:jbossweb
Recommend upgrading to a component version not impacted by this vulnerability.