Vulnerability in org.apache.tomcat:tomcat (CVE-2020-13934)
Summary
Vulnerability in org.apache.tomcat:tomcat (CVE-2020-13934). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 8.5.56 or later.
Original description
The description as published by the source.
An h2c direct connection to Apache Tomcat 10.0.0 to 10.0.0, 9.0.0 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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2020-13934 has been found in org.apache.tomcat:tomcat.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade org.apache.tomcat:tomcat to 8.5.56 or later.
If unsure, ask your IT team or search "org.apache.tomcat:tomcat CVE-2020-13934" on the vendor's site.
CVE-2020-13934 (org.apache.tomcat:tomcat) — CWE-401 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 8.5.56 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-401) exists in org.apache.tomcat:tomcat.
Check the vendor advisory for the affected versions of org.apache.tomcat:tomcat.
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure.
Update to 8.5.56.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで org.apache.tomcat:tomcat を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade org.apache.tomcat:tomcat to 8.5.56ステージング環境で 8.5.56 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Ubuntu UBUNTU-CVE-2020-13934 tomcat8
References
- advisory lists.apache.org
- advisory lists.debian.org
- advisory debian.org
- advisory oracle.com
- advisory oracle.com
- advisory lists.opensuse.org
- advisory lists.opensuse.org
- advisory oracle.com
- advisory oracle.com
- advisory oracle.com
- advisory security.netapp.com
- advisory usn.ubuntu.com
- package github.com
- web nvd.nist.gov
- web lists.apache.org
- web security.netapp.com
- web usn.ubuntu.com
- web github.com
- web lists.apache.org