← Back
CVE-2024-10906
Cross-Site Request Forgery (CSRF) in dbgpt (CVE-2024-10906)
Summary
vulnerability in dbgpt (CVE-2024-10906). Data can be tampered with by attackers. Exploitable via ``uvicorn``.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-10906** has been found in dbgpt.
Attackers can target a specific entry point like ``uvicorn`` over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: ?/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "dbgpt CVE-2024-10906" on the vendor's site.
CVE-2024-10906 (dbgpt) — CWE-352 /
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: `uvicorn` / `dbgpt_server` / `CORSMiddleware`
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
**CSRF** (CWE-352) exists in dbgpt. Attackers reach the vulnerable code path via ``uvicorn`` without authentication.
📍 Affected scope
dbgpt — . Attack surface: `uvicorn` / `dbgpt_server` / `CORSMiddleware`.
🔥 Severity
Severity: ?. Data can be tampered with by attackers
🔧 How to fix
Update to the patched release per vendor advisory.
🛡️ 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 'dbgpt' .` 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 'dbgpt' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `dbgpt` を grep し、稼働しているサービス・バージョンを把握する。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
dbgpt
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"0.6.0"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2024-10906
- advisory https://github.com/advisories/GHSA-3248-f932-c76p
- package https://github.com/eosphoros-ai/DB-GPT
- package https://pypi.org/project/dbgpt
- web https://github.com/eosphoros-ai/DB-GPT/blob/f5de05b2636bc0628b3a92d32b22a26f88a18f2a/dbgpt/app/dbgpt_server.py#L240
- web https://huntr.com/bounties/8864aca5-a342-4dab-b866-b2882ba6f160