# CVE-2024-10829: Denial of Service (DoS) via Multipart Boundary in eosphoros-ai/db-gpt

> Unauthenticated attackers can cause a denial of service by sending malformed multipart boundaries, triggering an infinite loop in the db-gpt library.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Mar 2025
- **Updated:** 15 Oct 2025
- **Also known as:** GHSA-6xgj-c5fx-5v57, PYSEC-2026-1290

## What is CVE-2024-10829?

CVE-2024-10829 is a high-severity denial of service vulnerability in eosphoros-ai/db-gpt, published on 20 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A Denial of Service (DoS) vulnerability in the multipart request boundary processing mechanism of eosphoros-ai/db-gpt v0.6.0 allows unauthenticated attackers to cause excessive resource consumption. The server fails to handle excessive characters appended to the end of multipart boundaries, leading to an infinite loop and complete denial of service for all users. This vulnerability affects all endpoints processing multipart/form-data requests.

Weakness: CWE-835 (Loop with Unreachable Exit Condition)

## Which versions are affected by CVE-2024-10829?

3 open source packages ship an affected version, including dbgpt. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `dbgpt` | PyPI | All versions to 0.6.0 | None |
| `dbgpt` | PyPI | All versions to 0.6.0 | None |
| `dbgpt` | PyPI | All versions to 0.6.0 | None |

Products: Dbgpt Db-Gpt.

## How do I fix CVE-2024-10829?

No fix has been published for CVE-2024-10829 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-10829 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-10829 exists.

Public exploit code:

- CVE-2024-10829 analysis (github_poc): https://github.com/junn34/POC_CVE-2024-10829

## Other vulnerabilities in eosphoros-ai/db-gpt

- [CVE-2024-10831](https://insights.sbomify.com/CVE-2024-10831/): Arbitrary File Write through Absolute Path Traversal in eosphoros-ai/db-gpt (critical 9.1)
- [CVE-2024-10833](https://insights.sbomify.com/CVE-2024-10833/): Arbitrary File Write in eosphoros-ai/db-gpt (critical 9.1)
- [CVE-2024-10834](https://insights.sbomify.com/CVE-2024-10834/): Arbitrary File Write in eosphoros-ai/db-gpt (critical 9.1)
- [CVE-2024-10835](https://insights.sbomify.com/CVE-2024-10835/): Arbitrary File Write via SQL Injection in eosphoros-ai/db-gpt (critical 9.1)
- [CVE-2024-10901](https://insights.sbomify.com/CVE-2024-10901/): Arbitrary File Write via DuckDB SQL Injection in eosphoros-ai/db-gpt (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-10829 and fix it if it is affected.

What it is: CVE-2024-10829 is a high-severity denial of service vulnerability in eosphoros-ai/db-gpt, published on 20 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-10829 exists.

Affected packages and fixed versions:
- dbgpt (PyPI): affected all versions up to 0.6.0; no fix listed
- dbgpt (PyPI): affected all versions up to 0.6.0; no fix listed
- dbgpt (PyPI): affected all versions up to 0.6.0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-10829/ (Markdown: https://insights.sbomify.com/CVE-2024-10829/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-10829
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-10829
- OSV: https://osv.dev/vulnerability/CVE-2024-10829

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-10829/
Summaries are generated and may contain mistakes; the official description above is the record.