Skip to content
Noroxi
NVD / CVE Program· CNA apache

CVE-2020-9484: 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…

HighCVSS 7.0 · v3.1—Proof of concept Fix available

Noroxi assessment

Priority: Plan (action score 45/100)

  • A ready-made attack module is public (Nuclei); exploiting it takes no special expertise.
  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 55.5% (FIRST EPSS); higher than 99% of all records.
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: tomcat9 (Debian:10) 9.0.31-1~deb10u2; tomcat9 (Debian:12) 9.0.35-1; tomcat7 (Debian:8) 7.0.56-3+really7.0.100-1+deb8u1.
  • Mentioned 5 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Add it to your regular patch cycle. Upgrade to tomcat9 (Debian:10) 9.0.31-1~deb10u2; tomcat9 (Debian:12) 9.0.35-1; tomcat7 (Debian:8) 7.0.56-3+really7.0.100-1+deb8u1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
May 20, 2020
Updated
Oct 8, 2026
EPSS
55.5% · 99th percentile

Report tools

JSON

Action score

45

Plan

Add it to your regular patch cycle.

CVSS
28 / 40 · 7.0 / 10
CISA KEV
0 / 30 · Not listed
EPSS
17 / 30 · 55.5%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2020-9484

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
apachetomcat
debiandebian linux
opensuseleap
fedoraprojectfedora
canonicalubuntu linux
oracleagile engineering data management
oracleagile product lifecycle management
oraclecommunications cloud native core binding support function
oraclecommunications cloud native core policy
oraclecommunications diameter signaling router
oraclecommunications element manager
oraclecommunications instant messaging server

and 14 more

Versions reported by the vendor

Affected version ranges reported by the assigning authority (apache). Independent of NVD's CPE analysis and usually ahead of it.

  • n/a Apache Tomcat

    • 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.103affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:10tomcat9before 9.0.31-1~deb10u29.0.31-1~deb10u2
Debian:12tomcat9before 9.0.35-19.0.35-1
Debian:8tomcat7before 7.0.56-3+really7.0.100-1+deb8u17.0.56-3+really7.0.100-1+deb8u1
Debian:8tomcat8before 8.0.14-1+deb8u178.0.14-1+deb8u17
Debian:9tomcat8before 8.5.54-0+deb9u28.5.54-0+deb9u2
Mavenorg.apache.tomcat:tomcat-catalinafrom 10.0.0-M1 · before 10.0.0-M510.0.0-M5
Mavenorg.apache.tomcat:tomcat-catalinafrom 7.0.0 · before 7.0.1047.0.104
Mavenorg.apache.tomcat:tomcat-catalinafrom 8.0.0 · before 8.5.558.5.55
Mavenorg.apache.tomcat:tomcat-catalinafrom 9.0.0 · before 9.0.359.0.35
Mavenorg.apache.tomcat.embed:tomcat-embed-corefrom 10.0.0-M1 · before 10.0.0-M510.0.0-M5
Mavenorg.apache.tomcat.embed:tomcat-embed-corefrom 7.0.0 · before 7.0.1047.0.104
Mavenorg.apache.tomcat.embed:tomcat-embed-corefrom 8.0.0 · before 8.5.558.5.55
Mavenorg.apache.tomcat.embed:tomcat-embed-corefrom 9.0.0 · before 9.0.359.0.35
openSUSE:Leap 15.1tomcatbefore 9.0.35-lp151.3.18.19.0.35-lp151.3.18.1
Red Hat:enterprise_linux:6::clienttomcat6before 0:6.0.24-115.el6_100:6.0.24-115.el6_10
Red Hat:enterprise_linux:6::clienttomcat6-admin-webappsbefore 0:6.0.24-115.el6_100:6.0.24-115.el6_10
Red Hat:enterprise_linux:6::clienttomcat6-docs-webappbefore 0:6.0.24-115.el6_100:6.0.24-115.el6_10
Red Hat:enterprise_linux:6::clienttomcat6-el-2.1-apibefore 0:6.0.24-115.el6_100:6.0.24-115.el6_10
Red Hat:enterprise_linux:6::clienttomcat6-javadocbefore 0:6.0.24-115.el6_100:6.0.24-115.el6_10
Red Hat:enterprise_linux:6::clienttomcat6-jsp-2.1-apibefore 0:6.0.24-115.el6_100:6.0.24-115.el6_10
Red Hat:enterprise_linux:6::clienttomcat6-libbefore 0:6.0.24-115.el6_100:6.0.24-115.el6_10
Red Hat:enterprise_linux:6::clienttomcat6-servlet-2.5-apibefore 0:6.0.24-115.el6_100:6.0.24-115.el6_10
Red Hat:enterprise_linux:6::clienttomcat6-webappsbefore 0:6.0.24-115.el6_100:6.0.24-115.el6_10
Red Hat:enterprise_linux:7::clienttomcatbefore 0:7.0.76-12.el7_80:7.0.76-12.el7_8

+96

Other highest-scoring records for the same primary product.

  • CVE-2025-24813Apache Tomcat: Potential RCE and/or information disclosure and/or information corruption with partial PUTKEV
    99Now
  • CVE-2016-8735Remote code execution is possible with Apache Tomcat before 6.0.48, 7.x before 7.0.73, 8.x before 8.0.39, 8.5.x before 8.5.7, and 9.x…KEV
    96Now
  • CVE-2017-12617When running Apache Tomcat versions 9.0.0.M1 to 9.0.0, 8.5.0 to 8.5.22, 8.0.0.RC1 to 8.0.46 and 7.0.0 to 7.0.81 with HTTP PUTs enabled (e.g.KEV
    92Now

Published before and after this one in the same product

  • ← EarlierCVE-2019-17569Feb 24, 2020 · The refactoring present in Apache Tomcat 9.0.28 to 9.0.30, 8.5.48 to 8.5.50 and 7.0.98 to 7.0.99 introduced a regression.
    22Monitor
  • ← EarlierCVE-2020-1935Feb 24, 2020 · In Apache Tomcat 9.0.0.M1 to 9.0.30, 8.5.0 to 8.5.50 and 7.0.0 to 7.0.99 the HTTP header parsing code used an approach to end-of-line…
    22Monitor
  • Later →CVE-2020-11996Jun 26, 2020 · A specially crafted sequence of HTTP/2 requests sent to Apache Tomcat 10.0.0-M1 to 10.0.0-M5, 9.0.0.M1 to 9.0.35 and 8.5.0 to 8.5.55 could…
    38Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:tomcat77.0.56-3+really7.0.100-1+deb8u1 · Debian:8Package registry (OSV)
debian:tomcat88.0.14-1+deb8u17 · Debian:8Package registry (OSV)
debian:tomcat99.0.35-1 · Debian:12Package registry (OSV)
Maven:org.apache.tomcat:tomcat-catalina10.0.0-M5Package registry (OSV)
Maven:org.apache.tomcat:tomcat-catalina7.0.104Package registry (OSV)
Maven:org.apache.tomcat:tomcat-catalina8.5.55Package registry (OSV)
Maven:org.apache.tomcat:tomcat-catalina9.0.35Package registry (OSV)
Maven:org.apache.tomcat.embed:tomcat-embed-core10.0.0-M5Package registry (OSV)
Maven:org.apache.tomcat.embed:tomcat-embed-core7.0.104Package registry (OSV)
Maven:org.apache.tomcat.embed:tomcat-embed-core8.5.55Package registry (OSV)
Maven:org.apache.tomcat.embed:tomcat-embed-core9.0.35Package registry (OSV)
opensuse:tomcat9.0.35-lp151.3.18.1 · openSUSE:Leap 15.1Package registry (OSV)
red hat:tomcat-native0:1.2.23-22.redhat_22.ep7.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6Package registry (OSV)
red hat:tomcat-native-debuginfo0:1.2.23-22.redhat_22.ep7.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6Package registry (OSV)
red hat:tomcat70:7.0.70-40.ep7.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6Package registry (OSV)
red hat:tomcat7-admin-webapps0:7.0.70-40.ep7.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6Package registry (OSV)
red hat:tomcat7-docs-webapp0:7.0.70-40.ep7.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6Package registry (OSV)
red hat:tomcat7-el-2.2-api0:7.0.70-40.ep7.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6Package registry (OSV)
red hat:tomcat7-javadoc0:7.0.70-40.ep7.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6Package registry (OSV)
red hat:tomcat7-jsp-2.2-api0:7.0.70-40.ep7.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6Package registry (OSV)
red hat:tomcat7-jsvc0:7.0.70-40.ep7.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6Package registry (OSV)
red hat:tomcat7-lib0:7.0.70-40.ep7.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6Package registry (OSV)
red hat:tomcat7-log4j0:7.0.70-40.ep7.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6Package registry (OSV)
red hat:tomcat7-selinux0:7.0.70-40.ep7.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6Package registry (OSV)
suse:tomcat9.0.35-4.30.2 · SUSE:Linux Enterprise Module for Web and Scripting 15 SP1Package registry (OSV)
suse:tomcat66.0.53-0.57.16.1 · SUSE:Linux Enterprise Point of Sale 11 SP3Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Nuclei detection template ×1
  • Proof-of-concept repository on GitHub ×17

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHub17 repositories2020-05-19 → 2024-10-06
Nuclei detection templateNuclei template CVE-2020-9484 —

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. First PoC-2 d
  2. Published
  3. TodayNov 16, 2026+2370 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

CVSS vector

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

nvd-primary

Root cause

Data received over the network is deserialized into the language’s native object format without verifying its source. Code paths inside the object can be triggered during deserialization.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

python
payload = sock.recv(65536)job = pickle.loads(payload)

Fixed

python
payload = sock.recv(65536)if not hmac.compare_digest(sign(payload), header_sig):    raise PermissionError("invalid signature")job = JobSchema.validate(json.loads(payload))

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

References

Show all references (19 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records