← Back
CVE-2025-9784
high
CVSS 7.5
Vulnerability in io.undertow:undertow-core (CVE-2025-9784)
Summary
vulnerability in io.undertow:undertow-core (CVE-2025-9784). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `2.3.20.Final` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-9784** has been found in io.undertow:undertow-core.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade io.undertow:undertow-core to **2.3.20.Final** or later.
If unsure, ask your IT team or search "io.undertow:undertow-core CVE-2025-9784" on the vendor's site.
CVE-2025-9784 (io.undertow:undertow-core) — CWE-770 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: `2.3.20.Final` — 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-770) exists in io.undertow:undertow-core.
📍 Affected scope
io.undertow:undertow-core — .
🔥 Severity
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **2.3.20.Final**.
🛡️ 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.undertow:undertow-core' .` 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.undertow:undertow-core' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `io.undertow:undertow-core` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade io.undertow:undertow-core to 2.3.20.Finalステージング環境で 2.3.20.Final に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
maven
io.undertow:undertow-core
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.3.20.Final"}]}]
References
- issue [email protected]
- patch [email protected]
- web [email protected]
- web [email protected]
- web [email protected]
- web [email protected]
- web [email protected]
- web [email protected]
- web [email protected]
- web [email protected]
- web [email protected]
- web [email protected]
- web [email protected]
- web [email protected]
- web [email protected]
- web [email protected]
- web [email protected]
- web af854a3a-2127-422b-91ae-364da2661108
- web https://nvd.nist.gov/vuln/detail/CVE-2025-9784
- web https://github.com/undertow-io/undertow/pull/1802
- web https://github.com/undertow-io/undertow/pull/1803
- web https://github.com/undertow-io/undertow/pull/1804
- web https://github.com/undertow-io/undertow/pull/1805
- web [email protected]
- web [email protected]
- web https://github.com/advisories/GHSA-95h4-w6j8-2rp8