CVE-2024-10901
Arbitrary File Write via DuckDB SQL Injection in eosphoros-ai/db-gpt
Public exploit available. Not confirmed exploited in the wild yet. No fix published yet.
What to do
No fixed build or workaround is published yet. Limit exposure and watch for a patch.
- Eosphoros-ai/db-gptAffected: ≥ unspecified, ≤ latestUpgrade to: after latestStated by: CVE record
- PyPI dbgptAffected: ≤ 0.6.3Upgrade to: after 0.6.3Stated by: GitHub advisory
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
In eosphoros-ai/db-gpt version v0.6.0, the web API `POST /api/v1/editor/chart/run` allows execution of arbitrary SQL queries without any access control. This vulnerability can be exploited by attackers to perform Arbitrary File Write, enabling them to write arbitrary files to the victim's file system. This can potentially lead to Remote Code Execution (RCE) by writing malicious files such as `__init__.py` in the Python's `/site-packages/` directory.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
1 source with a proof of concept or module.
Exploit links, PoCs and Metasploit modules after sign-in- EPSS
1.1% chance of exploitation activity in the next 30 days, which ranks it in the 65th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
5 events over 351 days, from the signal feeds we watch.
- Public exploit / PoCsource: other
- Record updated
- Publishedweakness classified, att&ck mapped
Affected products
Technical detail
CVSS 3.1 vector
Open in the CVSS calculatorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Scored 9.8 by NVD.
How it is reached
- Attack Vector NetworkExploitable remotely over the network without any special conditions
- Attack Complexity LowNo special conditions — the attack can be reliably reproduced
- Privileges Required NoneNo authentication required — anyone can exploit this
- User Interaction NoneNo user interaction needed — fully automated exploitation
Scope
- Scope UnchangedImpact is limited to the vulnerable component itself
Impact if exploited
- Confidentiality HighTotal information disclosure — all data in the component is compromised
- Integrity HighTotal loss of integrity — attacker can modify any data in the component
- Availability HighTotal denial of service — the component is completely unavailable
Weaknesses
ATT&CK techniques
Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.
- Command and ControlT1105Ingress Tool Transferhigh confidence
- Initial AccessT1190Exploit Public-Facing Applicationhigh confidence
- PersistenceT1505Server Software Componenthigh confidence
Sources
References in the record
- huntr.com/bounties/db2c1d59-6e3a-4553-a1f6-94c8df162a18
- nvd.nist.gov/vuln/detail/CVE-2024-10901
- github.com/eosphoros-ai/DB-GPT/pull/2269
And 2 more references. See all after sign-in
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Eosphoros-ai/db-gpt, not every advisory. This one: public exploit.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI