VulnerabilityPublished 10 Jul 2024Updated 15 Oct 2025

CVE-2024-6037: gaizhenbiao/chuanhuchatgpt · Unthrottled Resource Allocation

Affects gaizhenbiao/chuanhuchatgptSource CVE Database V5

Not known to be exploited · 10% EPSS · CVSS 7.5 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.0 base score

7.5High

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

EPSS: 10.6% chance of exploitation in 30 days – higher than 95% 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 10 Jul 2024
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 26 Oct 2026.

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 or the CVSS exploit maturity 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
GitHubgaizhenbiao/chuanhuchatgpt`pkg:github/gaizhenbiao/chuanhuchatgpt`Other threats	Affected =20240410	Fixed in–

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

AI-suggested

To mitigate CVE-2024-6037 effectively, European organizations should implement several targeted measures beyond generic advice: 1) Immediately restrict network access to the gaizhenbiao/chuanhuchatgpt service to trusted IP ranges and internal networks to reduce exposure. 2) Employ strict filesystem permissions and access controls to prevent unauthorized folder creation, especially restricting write permissions on critical directories such as the root or system folders. 3) Monitor filesystem activity for unusual or unauthorized directory creation using host-based intrusion detection systems (HIDS) or file integrity monitoring tools. 4) Implement resource usage monitoring and alerting to detect abnormal disk space consumption or inode exhaustion early. 5) If possible, deploy application-layer firewalls or reverse proxies to filter and validate incoming requests to the vulnerable service, blocking suspicious payloads that attempt directory creation. 6) Engage with the vendor or community to obtain patches or updates addressing this vulnerability and plan for rapid deployment once available. 7) Conduct regular security audits and penetration testing focusing on filesystem permissions and resource allocation controls in the affected environment. 8) Educate system administrators and security teams about this vulnerability to ensure prompt detection and response. These steps, combined, will reduce the attack surface and limit the potential damage from exploitation.

Description

A vulnerability in gaizhenbiao/chuanhuchatgpt version 20240410 allows an attacker to create arbitrary folders at any location on the server, including the root directory (C: dir). This can lead to uncontrolled resource consumption, resulting in resource exhaustion, denial of service (DoS), server unavailability, and potential data loss or corruption.

Impact

For European organizations, the impact of CVE-2024-6037 can be substantial, particularly for those relying on gaizhenbiao/chuanhuchatgpt in production environments. The ability for an unauthenticated attacker to create arbitrary folders anywhere on the server can lead to rapid resource exhaustion, causing denial of service and operational disruptions. This can affect availability of critical services, leading to downtime and potential financial losses. Additionally, if folder creation interferes with system or application files, data corruption or loss may occur, impacting data integrity and business continuity. Sectors such as finance, healthcare, and public administration, which require high availability and data integrity, could face severe consequences. The lack of required privileges or user interaction lowers the barrier for exploitation, increasing the risk of automated attacks. European organizations with limited visibility into filesystem changes or lacking strict access controls may be particularly vulnerable. Furthermore, the potential for cascading failures in interconnected systems raises concerns for critical infrastructure and cloud service providers within Europe.

CWE-770Allocation of Resources Without Limits or Throttling (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #25
The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.
Requirements
Clearly specify the minimum and maximum expectations for capabilities, and dictate which behaviors are acceptable when resource allocation reaches limits.
Architecture and Design
Limit the amount of resources that are accessible to unprivileged users. Set per-user limits for resources. Allow the system administrator to define these limits. Be careful to avoid CWE-410.
Architecture and Design
Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
OWASP ASVS 4.0.3
V8.1.4 (opens in a new tab)
V13.4.1 (opens in a new tab)
V11.1.4 (opens in a new tab)
Attack patterns
XML Ping of the Death (opens in a new tab)
Exponential Data Expansion (opens in a new tab)
Serialized Data Parameter Blowup (opens in a new tab)
Serialized Data with Nested Payloads (opens in a new tab)
Oversized Serialized Data Payloads (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

WeaknessesCWE-770

Technical details

References

Community reviews

Related threats