Last Updated: 2022-03-30 14:26:57 UTC
by Johannes Ullrich (Version: 1)
Last night, news broke that the Java Spring framework may release an update fixing a significant security vulnerability. The project added a patch to the Spring framework GitHub repository that appears to fix a deserialization vulnerability .
A blog post published around that time includes some additional details . However, the comment by Sam Brannon released with the git commit (scroll down to the end of the page for ) does explain the patch:
The purpose of this commit is to inform anyone who had previously been using
SerializationUtils#deserializethat it is dangerous to deserialize objects from untrusted sources.
The core Spring Framework does not use
SerializationUtilsto deserialize objects from untrusted sources.
There is no CVE and no official announcement from Spring at this time. But it may be a good idea to find your Log4j notes as your response will likely be similar.
Do not confuse this vulnerability with CVE-2022-22963 (I have already seen some posts mixing up the two). CVE-2022-22963 is a vulnerability in Spring Cloud Function, not in the spring framework. It was patched yesterday and appeared already to be probed based on our honeypot. For example, we do see requests like this:
THIS IS CVE-2022-22963, NOT spring4shell
POST /console/images/%252e%252e%252fconsole.portal HTTP/1.1
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.108 Safari/537.36