Unsafe Deserialization in org.apache.tomcat:tomcat-catalina (CVE-2020-9484)

Summary

vulnerability in org.apache.tomcat:tomcat-catalina (CVE-2020-9484). Successful exploitation can lead to full system takeover. Mitigation: upgrade to `7.0.104` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2020-9484** has been found in org.apache.tomcat:tomcat-catalina. Successful exploitation can lead to full system takeover. CVSS score: 7.0/10. What to do: upgrade org.apache.tomcat:tomcat-catalina to **7.0.104** or later. If unsure, ask your IT team or search "org.apache.tomcat:tomcat-catalina CVE-2020-9484" on the vendor's site.

CVE-2020-9484 (org.apache.tomcat:tomcat-catalina) — CWE-502 / CVSS v3 7.0 Attack vector: local / no user interaction Patched: `7.0.104` — 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.

❓ What is the problem

**unsafe deserialization** (CWE-502) exists in org.apache.tomcat:tomcat-catalina.

📍 Affected scope

org.apache.tomcat:tomcat-catalina — .

🔥 Severity

Severity: High (CVSS 7.0/10). Successful exploitation can lead to full system takeover

🔧 How to fix

Update to **7.0.104**.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'org.apache.tomcat:tomcat-catalina' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response Actions (7 steps)

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
grep -r 'org.apache.tomcat:tomcat-catalina' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `org.apache.tomcat:tomcat-catalina` を grep し、稼働しているサービス・バージョンを把握する。
6
Apply patch patch
```
Upgrade org.apache.tomcat:tomcat-catalina to 7.0.104
```
ステージング環境で 7.0.104 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
7
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

maven org.apache.tomcat:tomcat-catalina

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.0.104"}]}]

maven org.apache.tomcat.embed:tomcat-embed-core