← Back
CVE-2024-10901
Unrestricted File Upload in dbgpt (CVE-2024-10901)
Summary
vulnerability in dbgpt (CVE-2024-10901). Data can be tampered with by attackers. Exploitable via `POST /api/v1/editor/chart/run`.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-10901** has been found in dbgpt.
Attackers can target a specific entry point like `POST /api/v1/editor/chart/run` 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-10901" on the vendor's site.
CVE-2024-10901 (dbgpt) — CWE-434 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: POST /api/v1/editor/chart/run / `__init__.py`
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-434) exists in dbgpt. Attackers reach the vulnerable code path via `POST /api/v1/editor/chart/run` without authentication.
📍 Affected scope
dbgpt — . Attack surface: POST /api/v1/editor/chart/run / `__init__.py`.
🔥 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 `POST /api/v1/editor/chart/run` requests with malformed payloads or SQL meta-characters. 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 し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'POST /api/v1/editor/chart/run' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `POST /api/v1/editor/chart/run` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
7Post-deployment verification verify
Replay attack against POST /api/v1/editor/chart/run on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
dbgpt
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"0.6.3"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2024-10901
- advisory https://github.com/advisories/GHSA-7gj6-22m4-qfhx
- package https://github.com/eosphoros-ai/DB-GPT
- package https://pypi.org/project/dbgpt
- web https://github.com/eosphoros-ai/DB-GPT/pull/2269
- web https://github.com/eosphoros-ai/DB-GPT/commit/295cdb8723663d5b0954d5d1dfb4f02b7223b8ff
- web https://huntr.com/bounties/db2c1d59-6e3a-4553-a1f6-94c8df162a18