← Back
ROOT-APP-MAVEN-CVE-2024-22243
Vulnerability in io.root.org.springframework:spring-web (ROOT-APP-MAVEN-CVE-2024-22243)
Summary
vulnerability in io.root.org.springframework:spring-web (ROOT-APP-MAVEN-CVE-2024-22243). Confidential information can be exposed externally. Mitigation: upgrade to `6.0.11-root.io.2, 6.0.11-root.io.3, 6.0.11-root.io.4, 6.0.11-root.io.6, 6.1.1-root.io.2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **ROOT-APP-MAVEN-CVE-2024-22243** has been found in io.root.org.springframework:spring-web.
Confidential information can be exposed externally. CVSS score: ?/10.
What to do: upgrade io.root.org.springframework:spring-web to **6.0.11-root.io.2, 6.0.11-root.io.3, 6.0.11-root.io.4, 6.0.11-root.io.6, 6.1.1-root.io.2** or later.
If unsure, ask your IT team or search "io.root.org.springframework:spring-web ROOT-APP-MAVEN-CVE-2024-22243" on the vendor's site.
ROOT-APP-MAVEN-CVE-2024-22243 (io.root.org.springframework:spring-web) —
Attack vector: remote (network-reachable) / unauthenticated
Patched: `6.0.11-root.io.2, 6.0.11-root.io.3, 6.0.11-root.io.4, 6.0.11-root.io.6, 6.1.1-root.io.2` — 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 io.root.org.springframework:spring-web.
📍 Affected scope
io.root.org.springframework:spring-web — .
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to **6.0.11-root.io.2, 6.0.11-root.io.3, 6.0.11-root.io.4, 6.0.11-root.io.6, 6.1.1-root.io.2**.
🛡️ 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 'io.root.org.springframework:spring-web' .` 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 'io.root.org.springframework:spring-web' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `io.root.org.springframework:spring-web` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade io.root.org.springframework:spring-web to 6.0.11-root.io.2, 6.0.11-root.io.3, 6.0.11-root.io.4, 6.0.11-root.io.6, 6.1.1-root.io.2ステージング環境で 6.0.11-root.io.2, 6.0.11-root.io.3, 6.0.11-root.io.4, 6.0.11-root.io.6, 6.1.1-root.io.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Root:Maven
io.root.org.springframework:spring-web
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.0.11-root.io.2"},{"fixed":"6.0.11-root.io.3"},{"fixed":"6.0.11-root.io.4"},{"fixed":"6.0.11-root.io.6"},{"fixed":"6.1.1-root.io.2"}]}]