← Back
DEBIAN-CVE-2024-24549
Vulnerability in tomcat10 (DEBIAN-CVE-2024-24549)
Summary
vulnerability in tomcat10 (DEBIAN-CVE-2024-24549). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `10.1.6-1+deb12u2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **DEBIAN-CVE-2024-24549** has been found in tomcat10.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade tomcat10 to **10.1.6-1+deb12u2** or later.
If unsure, ask your IT team or search "tomcat10 DEBIAN-CVE-2024-24549" on the vendor's site.
DEBIAN-CVE-2024-24549 (tomcat10) —
Patched: `10.1.6-1+deb12u2` — 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
**A vulnerability** (unclassified) exists in tomcat10.
📍 Affected scope
tomcat10 — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **10.1.6-1+deb12u2**.
🛡️ 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 'tomcat10' .` 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
-
1Identify exposure identify
grep -r 'tomcat10' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `tomcat10` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade tomcat10 to 10.1.6-1+deb12u2ステージング環境で 10.1.6-1+deb12u2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Debian:12
tomcat10
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10.1.6-1+deb12u2"}]}]
Debian:13
tomcat10
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10.1.20-1"}]}]
Debian:14
tomcat10
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10.1.20-1"}]}]
Debian:11
tomcat9
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.0.43-2~deb11u10"}]}]
Debian:12
tomcat9
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.0.70-2"}]}]
Debian:13
tomcat9
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.0.70-2"}]}]
Debian:14
tomcat9
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.0.70-2"}]}]