Lucene search

K
attackerkbAttackerKBAKB:38F76C83-56D0-4112-A583-4513CC15B1B3
HistoryMay 20, 2020 - 12:00 a.m.

CVE-2020-9484 — PersistentManager Java deserialization vulnerability

2020-05-2000:00:00
attackerkb.com
26

0.922 High

EPSS

Percentile

99.0%

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.

Recent assessments:

redtimmy at June 06, 2020 1:41pm UTC reported:

This attack can have high impact (RCE), but the conditions that need to be met make the likelihood of exploitation low.

  1. PersistentManager needs to be enabled manually by the tomcat administrator. This is likely to happen only on websites with high traffic loads (but not too high, as it will be more likely that a JDBC Store is used instead of a File Store)

  2. The attacker has to find a separate file upload vulnerability to place the malicious serialized file on the server.

  3. There have to be libraries on the classpath which are vulnerable to be exploited by a Java deserialization attack (e.g. gadgets).

However, a large range of versions of tomcat are affected.

More info in this article: <https://www.redtimmy.com/java-hacking/apache-tomcat-rce-by-deserialization-cve-2020-9484-write-up-and-exploit/&gt;

wvu-r7 at June 07, 2020 12:22am UTC reported:

This attack can have high impact (RCE), but the conditions that need to be met make the likelihood of exploitation low.

  1. PersistentManager needs to be enabled manually by the tomcat administrator. This is likely to happen only on websites with high traffic loads (but not too high, as it will be more likely that a JDBC Store is used instead of a File Store)

  2. The attacker has to find a separate file upload vulnerability to place the malicious serialized file on the server.

  3. There have to be libraries on the classpath which are vulnerable to be exploited by a Java deserialization attack (e.g. gadgets).

However, a large range of versions of tomcat are affected.

More info in this article: <https://www.redtimmy.com/java-hacking/apache-tomcat-rce-by-deserialization-cve-2020-9484-write-up-and-exploit/&gt;

Assessed Attacker Value: 3
Assessed Attacker Value: 3Assessed Attacker Value: 3

References