dbcve.org
TomcatWeb server / proxy · Apache

CVE-2019-10072

HIGH · 7.5 CVSS v3.0 Published 2019-06-21
Fix available
A fix is available. Upgrade to after 9.0.19 or later.
See remediation →
84/100
Remediation priority · High
High EPSS Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The fix for CVE-2019-0199 was incomplete and did not address HTTP/2 connection window exhaustion on write in Apache Tomcat versions 9.0.0.M1 to 9.0.19 and 8.5.0 to 8.5.40 . By not sending WINDOW_UPDATE messages for the connection window (stream 0) clients were able to cause server-side threads to block eventually leading to thread exhaustion and a DoS.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In Apache Tomcat 9.0.0.M1-9.0.19 and 8.5.0-8.5.40, the incomplete fix for CVE-2019-0199 failed to address HTTP/2 connection window (stream 0) management. By not sending WINDOW_UPDATE messages for the connection window, attackers can cause server threads to block on writes, eventually leading to thread exhaustion and denial of service.

MitigationUpgrade to Apache Tomcat 9.0.20 or later, or 8.5.41 or later. If immediate upgrade is not possible, consider disabling HTTP/2 or implementing rate limiting on the load balancer.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
TomcatWeb server / proxy
Affected:>= 8.5.0, <= 8.5.40>= 9.0.1, <= 9.0.19= 9.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache Tomcat version
    Check the version.jar or run 'java -cp catalina.jar org.apache.catalina.util.ServerInfo' from the Tomcat lib directory, or inspect the RELEASE-NOTES file in the Tomcat home directory
    Affected if version is 8.5.0 through 8.5.40, or 9.0.0 through 9.0.19 (including 9.0.0.M1-Mn variants)
  2. Confirm HTTP/2 connector is configured
    Inspect the server.xml file in the conf directory and look for <Connector> elements with protocol="h2" or protocol="org.apache.coyote.http2.Http2Protocol"
    Affected if an HTTP/2 connector is defined and enabled in the configuration

You are affected if you are running Apache Tomcat 8.5.0-8.5.40 or 9.0.0-9.0.19 with an HTTP/2 connector configured and actively handling traffic.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 9.0.19
Interim mitigation

Upgrade to Apache Tomcat 9.0.20 or later, or 8.5.41 or later. If immediate upgrade is not possible, consider disabling HTTP/2 or implementing rate limiting on the load balancer.

Fix this in Tomcat Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-10072 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-10072 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data