SECUFOCUSNOW
Home›CVE index›CVE-2020-9484
Priority reviewHigh

CVE-2020-9484

Apache Tomcat, tomcat, debian linux

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 FileStor...

CVSS
7
EPSS
56.6%
99.0% percentile
CISA KEV
Not listed
Published
2020.05.21
PRIORITY ASSESSMENT

Priority review

FIRST EPSS indicates an elevated probability of exploitation.

Known exploitationNot established by KEV
Exploit probability56.6%
Technical severityCVSS 7

Vulnerability overview

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 FileStor...

Affected product and versions

Product
Apache Tomcat, tomcat, debian linux
Affected versions
>= Apache Tomcat 10.0.0-M1 to 10.0.0-M4, 9.0.0.M1 to 9.0.34, 8.5.0 to 8.5.54, 7.0.0 to 7.0.103, >= 7.0.0 < 7.0.108, >= 8.5.0 < 8.5.63, >= 9.0.1 < 9.0.43, 9.0.0, 10.0.0, 8.0, 9.0, 10.0, 15.1, 31, 32, 16.04, 20.04, 6.2.1.0, 9.3.3, 9.3.5, 9.3.6, 1.10.0, 1.14.0
Fixed versions
7.0.108, 8.5.63, 9.0.43

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Apache Tomcat, tomcat, debian linux and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
CWE-502