CVE-2019-0199
HIGHCVE-2019-0199 is a high-severity (CVSS 7.5) Uncontrolled Resource Consumption vulnerability in org.apache.tomcat.embed:tomcat-embed-core. O3 Security confirms whether CVE-2019-0199 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Apache Tomcat Denial of Service vulnerability
Real-World Exposure
org.apache.tomcat.embed:tomcat-embed-core☕org.apache.tomcat.embed:tomcat-embed-core☕org.apache.tomcat:tomcat-coyote☕org.apache.tomcat:tomcat-coyoteReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
The HTTP/2 implementation in Apache Tomcat 9.0.0.M1 to 9.0.14 and 8.5.0 to 8.5.37 accepted streams with excessive numbers of SETTINGS frames and also permitted clients to keep streams open without reading/writing request/response data. By keeping streams open for requests that utilised the Servlet API's blocking I/O, clients were able to cause server-side threads to block eventually leading to thread exhaustion and a DoS.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.tomcat.embed:tomcat-embed-core | ≥ 9.0.0&&< 9.0.16 | 9.0.16 |
| ☕Maven | org.apache.tomcat.embed:tomcat-embed-core | ≥ 8.0.0&&< 8.5.38 | 8.5.38 |
| ☕Maven | org.apache.tomcat:tomcat-coyote | ≥ 9.0.0&&< 9.0.16 | 9.0.16 |
| ☕Maven | org.apache.tomcat:tomcat-coyote | ≥ 8.0.0&&< 8.5.38 | 8.5.38 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.tomcat.embed:tomcat-embed-core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.apache.tomcat.embed:tomcat-embed-core to 9.0.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-0199 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2019-0199 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2019-0199. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
pki-servlet-container does not use HTTP/2 in its default configuration.
Frequently Asked Questions
Is CVE-2019-0199 in your dependencies?
O3 detects CVE-2019-0199 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.