Skip to content
Noroxi
NVD / CVE Program· CNA apache

CVE-2019-12418: When Apache Tomcat 9.0.0.M1 to 9.0.28, 8.5.0 to 8.5.47, 7.0.0 and 7.0.97 is configured with the JMX Remote Lifecycle Listener, a local…

HighCVSS 7.0 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 28/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 1.2% (FIRST EPSS); higher than 69.1% 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~deb10u1; tomcat9 (Debian:12) 9.0.31-1; tomcat7 (Debian:8) 7.0.56-3+really7.0.99-1.
  • Mentioned 3 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to tomcat9 (Debian:10) 9.0.31-1~deb10u1; tomcat9 (Debian:12) 9.0.31-1; tomcat7 (Debian:8) 7.0.56-3+really7.0.99-1 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 Apache Tomcat 9.0.0.M1 to 9.0.28, 8.5.0 to 8.5.47, 7.0.0 and 7.0.97 is configured with the JMX Remote Lifecycle Listener, a local attacker without access to the Tomcat process or configuration files is able to manipulate the RMI registry to perform a man-in-the-middle attack to capture user names and passwords used to access the JMX interface. The attacker can then use these credentials to access the JMX interface and gain complete control over the Tomcat instance.

Published
Dec 23, 2019
Updated
Oct 8, 2026
EPSS
1.2% · 69th percentile
CWE
—

Report tools

JSON

Action score

28

Monitor

Low priority for now.

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

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
  • No public exploit code on record
  • A fix has been released

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

Follow CVE-2019-12418

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
oracleworkload manager
canonicalubuntu linux
opensuseleap
netapponcommand system manager

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.

  • Apache Software Foundation Apache Tomcat

    • 9.0.0.M1 to 9.0.28, 8.5.0 to 8.5.47, 7.0.0 to 7.0.97affected

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~deb10u19.0.31-1~deb10u1
Debian:12tomcat9before 9.0.31-19.0.31-1
Debian:8tomcat7before 7.0.56-3+really7.0.99-17.0.56-3+really7.0.99-1
Debian:8tomcat8before 8.0.14-1+deb8u168.0.14-1+deb8u16
Debian:9tomcat8before 8.5.50-0+deb9u18.5.50-0+deb9u1
Mavenorg.apache.tomcat.embed:tomcat-embed-corefrom 8.0.0 · before 8.5.498.5.49
Mavenorg.apache.tomcat.embed:tomcat-embed-corefrom 9.0.0 · before 9.0.299.0.29
Mavenorg.apache.tomcat.embed:tomcat-embed-corebefore 7.0.997.0.99
openSUSE:Leap 15.1tomcatbefore 9.0.30-lp151.3.6.19.0.30-lp151.3.6.1
openSUSE:Tumbleweedtomcatbefore 9.0.36-8.49.0.36-8.4
Red Hat:jboss_enterprise_web_server:3.1::el6tomcat-nativebefore 0:1.2.23-21.redhat_21.ep7.el60:1.2.23-21.redhat_21.ep7.el6
Red Hat:jboss_enterprise_web_server:3.1::el6tomcat-native-debuginfobefore 0:1.2.23-21.redhat_21.ep7.el60:1.2.23-21.redhat_21.ep7.el6
Red Hat:jboss_enterprise_web_server:3.1::el6tomcat7before 0:7.0.70-38.ep7.el60:7.0.70-38.ep7.el6
Red Hat:jboss_enterprise_web_server:3.1::el6tomcat7-admin-webappsbefore 0:7.0.70-38.ep7.el60:7.0.70-38.ep7.el6
Red Hat:jboss_enterprise_web_server:3.1::el6tomcat7-docs-webappbefore 0:7.0.70-38.ep7.el60:7.0.70-38.ep7.el6
Red Hat:jboss_enterprise_web_server:3.1::el6tomcat7-el-2.2-apibefore 0:7.0.70-38.ep7.el60:7.0.70-38.ep7.el6
Red Hat:jboss_enterprise_web_server:3.1::el6tomcat7-javadocbefore 0:7.0.70-38.ep7.el60:7.0.70-38.ep7.el6
Red Hat:jboss_enterprise_web_server:3.1::el6tomcat7-jsp-2.2-apibefore 0:7.0.70-38.ep7.el60:7.0.70-38.ep7.el6
Red Hat:jboss_enterprise_web_server:3.1::el6tomcat7-jsvcbefore 0:7.0.70-38.ep7.el60:7.0.70-38.ep7.el6
Red Hat:jboss_enterprise_web_server:3.1::el6tomcat7-libbefore 0:7.0.70-38.ep7.el60:7.0.70-38.ep7.el6
Red Hat:jboss_enterprise_web_server:3.1::el6tomcat7-log4jbefore 0:7.0.70-38.ep7.el60:7.0.70-38.ep7.el6
Red Hat:jboss_enterprise_web_server:3.1::el6tomcat7-selinuxbefore 0:7.0.70-38.ep7.el60:7.0.70-38.ep7.el6
Red Hat:jboss_enterprise_web_server:3.1::el6tomcat7-servlet-3.0-apibefore 0:7.0.70-38.ep7.el60:7.0.70-38.ep7.el6
Red Hat:jboss_enterprise_web_server:3.1::el6tomcat7-webappsbefore 0:7.0.70-38.ep7.el60:7.0.70-38.ep7.el6

+80

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-10072Jun 21, 2019 · The fix for CVE-2019-0199 was incomplete and did not address HTTP/2 connection window exhaustion on write in Apache Tomcat versions…
    52Plan
  • ← EarlierCVE-2019-17563Dec 23, 2019 · When using FORM authentication with Apache Tomcat 9.0.0.M1 to 9.0.29, 8.5.0 to 8.5.49 and 7.0.0 to 7.0.98 there was a narrow window where…
    33Monitor
  • Later →CVE-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

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.99-1 · Debian:8Package registry (OSV)
debian:tomcat88.0.14-1+deb8u16 · Debian:8Package registry (OSV)
debian:tomcat99.0.31-1 · Debian:12Package registry (OSV)
Maven:org.apache.tomcat.embed:tomcat-embed-core7.0.99Package registry (OSV)
Maven:org.apache.tomcat.embed:tomcat-embed-core8.5.49Package registry (OSV)
Maven:org.apache.tomcat.embed:tomcat-embed-core9.0.29Package registry (OSV)
opensuse:tomcat9.0.30-lp151.3.6.1 · openSUSE:Leap 15.1Package registry (OSV)
red hat:tomcat-native0:1.2.23-21.redhat_21.ep7.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6Package registry (OSV)
red hat:tomcat-native-debuginfo0:1.2.23-21.redhat_21.ep7.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6Package registry (OSV)
red hat:tomcat70:7.0.70-38.ep7.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6Package registry (OSV)
red hat:tomcat7-admin-webapps0:7.0.70-38.ep7.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6Package registry (OSV)
red hat:tomcat7-docs-webapp0:7.0.70-38.ep7.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6Package registry (OSV)
red hat:tomcat7-el-2.2-api0:7.0.70-38.ep7.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6Package registry (OSV)
red hat:tomcat7-javadoc0:7.0.70-38.ep7.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6Package registry (OSV)
red hat:tomcat7-jsp-2.2-api0:7.0.70-38.ep7.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6Package registry (OSV)
red hat:tomcat7-jsvc0:7.0.70-38.ep7.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6Package registry (OSV)
red hat:tomcat7-lib0:7.0.70-38.ep7.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6Package registry (OSV)
red hat:tomcat7-log4j0:7.0.70-38.ep7.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6Package registry (OSV)
red hat:tomcat7-selinux0:7.0.70-38.ep7.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6Package registry (OSV)
suse:tomcat9.0.30-4.10.1 · 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

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

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.

No dated events beyond publication.

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: EPSS history · 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

Weakness class (CWE)

—

CVSS vector

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

nvd-primary

Attack context

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

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

All records