Deserialization of Untrusted Data Affecting tomcat-jsp-2_3-api package, versions <9.0.35-3.52.2



    Exploit Maturity Proof of concept
    Attack Complexity High
    Confidentiality High
    Integrity High
    Availability High
Expand this section
7 high
Expand this section
7.5 high
Expand this section
Red Hat
7 high

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk ID SNYK-SLES150-TOMCATJSP23API-2710976
  • published 14 Apr 2022
  • disclosed 21 May 2020

How to fix?

Upgrade SLES:15.0 tomcat-jsp-2_3-api to version 9.0.35-3.52.2 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream tomcat-jsp-2_3-api package and not the tomcat-jsp-2_3-api package as distributed by SLES:15.0. See How to fix? for SLES:15.0 relevant fixed versions and status.

When using Apache Tomcat versions 10.0.0-M1 to 10.0.0-M4, 9.0.0.M1 to 9.0.34, 8.5.0 to 8.5.54 and 7.0.0 to 7.0.103 if a) an attacker is able to control the contents and name of a file on the server; and b) the server is configured to use the PersistenceManager with a FileStore; and c) the PersistenceManager is configured with sessionAttributeValueClassNameFilter="null" (the default unless a SecurityManager is used) or a sufficiently lax filter to allow the attacker provided object to be deserialized; and d) the attacker knows the relative file path from the storage location used by FileStore to the file the attacker has control over; then, using a specifically crafted request, the attacker will be able to trigger remote code execution via deserialization of the file under their control. Note that all of conditions a) to d) must be true for the attack to succeed.