← Back
CVE-2024-52318
Vulnerability in org.apache.tomcat:tomcat-jasper (CVE-2024-52318)
Summary
vulnerability in org.apache.tomcat:tomcat-jasper (CVE-2024-52318). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `9.0.97` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-52318** has been found in org.apache.tomcat:tomcat-jasper.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade org.apache.tomcat:tomcat-jasper to **9.0.97** or later.
If unsure, ask your IT team or search "org.apache.tomcat:tomcat-jasper CVE-2024-52318" on the vendor's site.
CVE-2024-52318 (org.apache.tomcat:tomcat-jasper) — CWE-326 /
Attack vector: remote (network-reachable) / unauthenticated
Patched: `9.0.97` — 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** (CWE-326) exists in org.apache.tomcat:tomcat-jasper.
📍 Affected scope
org.apache.tomcat:tomcat-jasper — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **9.0.97**.
🛡️ 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-jasper' .` 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 'org.apache.tomcat:tomcat-jasper' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `org.apache.tomcat:tomcat-jasper` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade org.apache.tomcat:tomcat-jasper to 9.0.97ステージング環境で 9.0.97 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
maven
org.apache.tomcat:tomcat-jasper
[{"type":"ECOSYSTEM","events":[{"introduced":"9.0.96"},{"fixed":"9.0.97"}]}]
maven
org.apache.tomcat.embed:tomcat-embed-jasper
[{"type":"ECOSYSTEM","events":[{"introduced":"10.1.31"},{"fixed":"10.1.32"}]}]
maven
org.apache.tomcat:tomcat
[{"type":"ECOSYSTEM","events":[{"introduced":"9.0.96"},{"fixed":"9.0.97"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2024-52318
- package https://github.com/apache/tomcat
- web https://lists.apache.org/thread/co243cw1nlh6p521c5265cm839wkqdp9
- web https://github.com/apache/tomcat/commit/8d1fc4733a06d1a03b9d644c57010f2ec5f0df38
- web https://github.com/apache/tomcat/commit/9813c5dd3259183f659bbb83312a5cf673cc1ebf
- web https://github.com/apache/tomcat/commit/be8e32143a3159e78fe5463d09bb8e1b33bf2b1f
- web https://bz.apache.org/bugzilla/show_bug.cgi?id=69333
- web https://security.netapp.com/advisory/ntap-20250131-0009
- web http://www.openwall.com/lists/oss-security/2024/11/18/4
- web https://github.com/advisories/GHSA-f632-9449-3j4w