Threat Advisory: Spring4Shell

Mar 31, 2022
Written by Davinsi Labs

Scope of the vulnerability

As the world’s most popular Java lightweight open-source framework, Spring allows developers to focus on business logic and simplifies the development cycle of Java enterprise applications.

On 29/03/2022, a Chinese security researcher publicly posted a 0-day exploit for the Spring Core framework. This was subsequently deleted, but was already picked up by several other parties. This exploit was dubbed “Spring4Shell“.

Spring4Shell uses a vulnerable annotation RequestMapping in combination with Plain Old Java Objects. Due to this, an attacker could post a request with a malicious payload which enables a remote code execution (RCE) for the attacker to use on the compromised host.

This vulnerability (CVE-2022-22965) is the main focus of this threat advisory and not to be confused with CVE-2022-22963, which is a vulnerability in the Spring Cloud Function library.

Affected Versions

The vulnerability exists in the Spring core framework and the following requirements must be met:

  • The application uses JDK version greater or equal to 9.0.
  • The application uses the Spring Core framework up until v5.3.16 (latest version).
  • The application uses form binding with name=value pairs instead of the message conversion system of JSON/XML.

Not affected

If on the running server of the organization system, the “java -version” command outputs a number less than or equal to 8, it is not affected by the vulnerability.


Spring Framework 5.3.18 and 5.2.20 have been released.
Both versions address the vulnerability and are already available on Maven Central.


The developers of Spring who maintain the Spring Core Framework, have published a blogpost regarding suggested workarounds which can be used as temporary remediation. The workarounds can be found here:


The bulk of attacks is related to mass scanning by attackers attempting to thumbprint vulnerable systems, as well as scanning by security companies and researchers.

Successful Spring4Shell exploitation may be detected through reverse proxy logs.

Monitor incoming, allowed POST requests containing class., .classloader. or request.getParameter(*) as a reliable and quick detection rule.

The full payload as seen in the POC may provide additional detection opportunities:

  1. “class.module.classLoader.resources.context.parent.pipeline
  2. .first.pattern=%25%7Bc2%7Di%20if(%22j%22.equals(request.getParameter(%
  3. 22pwd%22)))
  4. ime().exec(request.getParameter(%22cmd%22)).getInputStream()%3B%20int%
  5. 20a%20%3D%20-1%3B%20byte%5B%5D%20b%20%3D%20new%20byte%5B2048%5D%3B%20
  6. while((
  7. D%20%7D%20%25%7Bsuffix%7Di&class.module.classLoader.resources.context
  8. .parent.pipeline.first.suffix=.jsp&class.module.classLoader.resources
  10. assLoader.resources.context.parent.pipeline.first.prefix=tomcatwar&cl
  11. ass.module.classLoader.resources.context.parent.pipeline.first.fileDat
  12. eFormat=”


Post exploitation activity may be hunted for by monitoring suspicious traffic (f.e requests containing recon commands) to probable JSP webshells.

Threat advisory updates

This blog post will be continuously updated in case new findings are published.

Reach out to if you need any assistance from our team of security experts.

We hope the following threat advisory assists to react quickly to ongoing threats and urges the need for patching and security monitoring.


Share this news