CVE-2024-10829VulnerabilityPublished 20 Mar 2025Updated 15 Oct 2025

CVE-2024-10829: eosphoros-ai/db-gpt · Loop with Unreachable Exit Condition

Affects eosphoros-ai/db-gptSource CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.0 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.7% chance of exploitation in 30 days – higher than 54% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 20 Mar 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
GitHubeosphoros-ai/db-gpt`pkg:github/eosphoros-ai/db-gpt`Other threats	Affected =0.6.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Monitor vendor communications closely and apply official patches or updates as soon as they become available to address the vulnerability directly. 2. Implement strict input validation and enforce limits on multipart request boundary lengths at the application or web server level to prevent excessively long boundaries from being processed. 3. Deploy Web Application Firewalls (WAFs) with custom rules to detect and block malformed multipart/form-data requests that exhibit abnormal boundary lengths or patterns indicative of exploitation attempts. 4. Configure rate limiting and anomaly detection on endpoints handling multipart requests to reduce the risk of resource exhaustion from repeated attack attempts. 5. Conduct thorough code reviews and testing of multipart parsing logic to identify and fix any other potential infinite loop or resource exhaustion issues. 6. Isolate critical AI/data processing services behind reverse proxies or API gateways that can provide additional filtering and protection layers. 7. Maintain comprehensive logging and alerting for multipart request anomalies to enable rapid detection and response to exploitation attempts. 8. Educate development and security teams about CWE-835 and secure coding practices related to input parsing loops to prevent similar vulnerabilities in future releases.

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.

Impact

For European organizations utilizing eosphoros-ai/db-gpt, this vulnerability poses a significant risk of service disruption due to Denial of Service attacks. The infinite loop triggered by malformed multipart requests can exhaust server resources, leading to downtime and unavailability of critical AI or data processing services. This can impact business operations, customer experience, and potentially lead to financial losses, especially for organizations relying on real-time or high-availability systems. The unauthenticated nature of the exploit means attackers can launch attacks without prior access, increasing the threat from external adversaries. Additionally, the broad impact on all multipart/form-data endpoints expands the attack surface, making mitigation more challenging. In sectors such as finance, healthcare, and critical infrastructure within Europe, where AI-driven applications are increasingly integrated, the disruption could have cascading effects. Furthermore, regulatory compliance frameworks like GDPR emphasize service availability and data protection, so prolonged outages might also lead to compliance risks. Organizations must assess their exposure and prioritize remediation to maintain operational resilience.

References

huntr.com/bounties/e3a4a0ad-a2e0-497f-a2e0-e3c0ec7c4de4 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 15 Oct 2025, 13:18 UTC

WeaknessesCWE-835

Technical details

References

Community reviews

Related threats