Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven

CVE-2020-13934

HIGH

Improper Restriction of Operations within the Bounds of a Memory Buffer in Apache Tomcat

Also known asBIT-tomcat-2020-13934GHSA-vf77-8h7g-gghp
Published
Jul 14, 2020
Updated
Apr 16, 2026
Affected
6 pkgs
Patched
6 / 6
Exploits
None indexed

EPSS Exploitation Probability

via FIRST.org ↗
64.1%probability of exploitation in next 30 days
High Risk99th percentile+40.74%
0.00%27.2%54.4%81.5%6.1%64.1%Dec 25Apr 26Jun 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

6 pkgs affected
org.apache.tomcat:tomcatorg.apache.tomcat:tomcatorg.apache.tomcat:tomcatorg.apache.tomcat:tomcat-coyoteorg.apache.tomcat:tomcat-coyoteorg.apache.tomcat:tomcat-coyote

Real-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

An h2c direct connection to Apache Tomcat 10.0.0-M1 to 10.0.0-M6, 9.0.0.M5 to 9.0.36 and 8.5.1 to 8.5.56 did not release the HTTP/1.1 processor after the upgrade to HTTP/2. If a sufficient number of such requests were made, an OutOfMemoryException could occur leading to a denial of service.

Affected Packages

6 total 6 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.apache.tomcat:tomcat10.0.0-M1&&< 10.0.0-M610.0.0-M6
Mavenorg.apache.tomcat:tomcat9.0.0.M5&&< 9.0.369.0.36
Mavenorg.apache.tomcat:tomcat8.5.1&&< 8.5.568.5.56
Mavenorg.apache.tomcat:tomcat-coyote10.0.0-M1&&< 10.0.0-M610.0.0-M6
Mavenorg.apache.tomcat:tomcat-coyote9.0.0.M5&&< 9.0.369.0.36
Mavenorg.apache.tomcat:tomcat-coyote8.5.1&&< 8.5.568.5.56

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.tomcat:tomcat. 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.

  2. Fix

    Update org.apache.tomcat:tomcat to 10.0.0-M6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-13934 is resolved across your whole dependency graph.

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

  4. How O3 protects you

    O3 pinpoints whether CVE-2020-13934 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-2020-13934. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

An h2c direct connection to Apache Tomcat 10.0.0-M1 to 10.0.0-M6, 9.0.0.M5 to 9.0.36 and 8.5.1 to 8.5.56 did not release the HTTP/1.1 processor after the upgrade to HTTP/2. If a sufficient number of such requests were made, an OutOfMemoryException could occur leading to a denial of service.
O3 Security · Impact-Aware SCA

Is CVE-2020-13934 in your dependencies?

O3 detects CVE-2020-13934 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.