CONTENTUM.COMA specialist. A plan. A result.

Vulnerabilities · 2020 · Apache

CVE-2020-9484
Apache Tomcat vulnerability

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.

Affected products

Tomcat, Debian Linux, Leap, Fedora, Ubuntu Linux, Agile Engineering Data Management, Agile Plm, Communications Cloud Native Core Binding Support Function, Communications Cloud Native Core Policy, Communications Diameter Signaling Router and more. The exact versions are in the references.

What to do now

  • Check your exposureFind out whether Apache Tomcat runs anywhere in your environment, including systems of suppliers.
  • UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
  • Set the orderSystems that can be reached from the internet come first, then the rest.

References

More vulnerabilities in Apache products

Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.