Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2024-10714: CWE-770 Allocation of Resources Without Limits or Throttling in binary-husky binary-husky/gpt_academic

0
High
VulnerabilityCVE-2024-10714cvecve-2024-10714cwe-770
Published: Thu Mar 20 2025 (03/20/2025, 10:10:35 UTC)
Source: CVE Database V5
Vendor/Project: binary-husky
Product: binary-husky/gpt_academic

Description

A vulnerability in binary-husky/gpt_academic version 3.83 allows an attacker to cause a Denial of Service (DoS) by adding excessive characters to the end of a multipart boundary during file upload. This results in the server continuously processing each character and displaying warnings, rendering the application inaccessible. The issue occurs when the terminal shows a warning: 'multipart.multipart Consuming a byte '0x2d' in end state'.

AI-Powered Analysis

AILast updated: 10/15/2025, 13:16:58 UTC

Technical Analysis

CVE-2024-10714 is a resource exhaustion vulnerability classified under CWE-770, affecting the binary-husky/gpt_academic software version 3.83 (and potentially other unspecified versions). The vulnerability arises during the handling of multipart file uploads, where an attacker can append an excessive number of characters to the end of a multipart boundary. The multipart parser in the application does not impose limits or throttling on the processing of these characters, causing the server to continuously consume resources while processing each appended byte. This results in the server repeatedly logging warnings such as 'multipart.multipart Consuming a byte '0x2d' in end state' and ultimately leads to Denial of Service by making the application unresponsive or inaccessible. The attack vector is network-based, requiring no authentication or user interaction, and the vulnerability has a CVSS 3.0 score of 7.5, indicating high severity. Although no public exploits are currently known, the vulnerability poses a significant risk due to its ease of exploitation and potential to disrupt service availability. The root cause is the lack of proper input validation and resource management in the multipart upload processing logic, which fails to limit the amount of data processed in boundary parsing. This vulnerability highlights the importance of implementing strict limits and throttling mechanisms when handling multipart data to prevent resource exhaustion attacks.

Potential Impact

For European organizations, particularly those in academia, research, or any sector utilizing binary-husky/gpt_academic, this vulnerability can lead to significant service outages. The Denial of Service condition can disrupt critical academic workflows, data processing, or collaborative projects relying on this software. Since the attack requires no authentication and can be launched remotely, it increases the risk of widespread disruption. Organizations may face operational downtime, loss of productivity, and potential reputational damage if services become unavailable. Additionally, prolonged DoS conditions could indirectly affect data integrity if recovery procedures are not properly managed. The impact is primarily on availability, with no direct confidentiality or integrity compromise reported. However, service unavailability in academic or research environments can have cascading effects on dependent systems and users across Europe.

Mitigation Recommendations

To mitigate CVE-2024-10714, organizations should prioritize applying vendor patches once available. In the absence of patches, implement strict input validation on multipart file uploads to reject requests with abnormally long or malformed multipart boundaries. Deploy rate limiting and throttling mechanisms on upload endpoints to prevent resource exhaustion from excessive data processing. Monitoring and alerting on unusual multipart upload activity can help detect exploitation attempts early. Network-level controls such as Web Application Firewalls (WAFs) can be configured to block suspicious multipart requests or limit the size and frequency of uploads. Additionally, consider isolating the vulnerable service behind reverse proxies that can enforce stricter request validation. Regularly update and audit multipart parsing libraries and dependencies to ensure known vulnerabilities are addressed. Finally, conduct penetration testing and resilience assessments to verify the effectiveness of implemented mitigations.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
@huntr_ai
Date Reserved
2024-11-01T22:00:57.121Z
Cvss Version
3.0
State
PUBLISHED

Threat ID: 68ef9b22178f764e1f470a3d

Added to database: 10/15/2025, 1:01:22 PM

Last enriched: 10/15/2025, 1:16:58 PM

Last updated: 10/16/2025, 2:25:28 PM

Views: 3

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats