CVE-2024-6038VulnerabilityPublished 27 Jun 2024Updated 15 Oct 2025

CVE-2024-6038: gaizhenbiao/chuanhuchatgpt · ReDoS

Affects gaizhenbiao/chuanhuchatgptSource CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.0 base score

7.5High

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

EPSS: 0.6% chance of exploitation in 30 days – higher than 51% 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 27 Jun 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 2026-10-25.

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

AI-suggested

To mitigate this vulnerability, organizations should implement strict input validation and sanitization on user-supplied keywords before they are used in regular expression operations. Limiting the complexity and length of regex patterns can prevent catastrophic backtracking. Employing regex libraries or engines that support timeouts or complexity limits can also reduce risk. If possible, refactor the filter_history function to avoid dynamic regex construction from untrusted input or replace regex matching with safer string matching techniques. Monitoring application performance and setting resource usage thresholds can help detect and mitigate ongoing attacks. Until an official patch is released, consider disabling or restricting access to the vulnerable feature. Additionally, applying network-level protections such as rate limiting and web application firewalls (WAFs) can help block suspicious requests containing malicious regex patterns. Regularly update the software and track vendor advisories for patches addressing this issue.

Description

A Regular Expression Denial of Service (ReDoS) vulnerability exists in the latest version of gaizhenbiao/chuanhuchatgpt. The vulnerability is located in the filter_history function within the utils.py module. This function takes a user-provided keyword and attempts to match it against chat history filenames using a regular expression search. Due to the lack of sanitization or validation of the keyword parameter, an attacker can inject a specially crafted regular expression, leading to a denial of service condition. This can cause severe degradation of service performance and potential system unavailability.

Impact

For European organizations, exploitation of this vulnerability could result in denial of service conditions affecting applications or services relying on gaizhenbiao/chuanhuchatgpt, particularly those that use the filter_history function for keyword-based chat history searches. This could disrupt business operations, degrade user experience, and potentially cause downtime in customer-facing or internal AI/chatbot systems. Given the network-exploitable nature, attackers could launch remote attacks causing service outages without needing credentials, increasing the risk of widespread disruption. Organizations in sectors heavily dependent on AI-driven communication tools, such as technology firms, customer support centers, and research institutions, may face operational and reputational damage. Additionally, the lack of input validation could be exploited as part of a broader attack chain to amplify denial of service effects. The impact is primarily on availability, with no direct confidentiality or integrity compromise reported.

Summary

CVE-2024-6038 identifies a Regular Expression Denial of Service (ReDoS) vulnerability in the gaizhenbiao/chuanhuchatgpt software, specifically within the filter_history function in utils.py. This function accepts a user-provided keyword and applies a regular expression search against chat history filenames. Because the keyword is not sanitized or validated, an attacker can supply a crafted regex pattern that triggers catastrophic backtracking during the regex evaluation. This inefficiency in the regex engine leads to excessive CPU consumption, causing severe degradation of service performance or complete denial of service. The vulnerability is remotely exploitable without requiring authentication or user interaction, increasing its risk profile. The CVSS v3.0 score of 7.5 reflects a high severity due to the network attack vector, low attack complexity, no privileges required, and no user interaction needed, with impact solely on availability. No patches or known exploits are currently documented, but the vulnerability is publicly disclosed and should be addressed promptly. The CWE-1333 classification highlights the root cause as inefficient regular expression complexity leading to resource exhaustion.

CWE-1333Inefficient Regular Expression Complexity (opens in a new tab)
Base weaknessLikelihood of exploit: High
The product uses a regular expression with a worst-case computational complexity that is inefficient and possibly exponential.
Architecture and Design
Use regular expressions that do not support backtracking, e.g. by removing nested quantifiers.
System Configuration
Set backtracking limits in the configuration of the regular expression implementation, such as PHP's pcre.backtrack_limit. Also consider limits on execution time for the process.
Implementation
Do not use regular expressions with untrusted input. If regular expressions must be used, avoid using backtracking in the expression.
OWASP Cheat Sheets
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V12.1.1 (opens in a new tab)
Attack patterns
Regular Expression Exponential Blowup (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

Description

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

WeaknessesCWE-1333

Technical details

References

Community reviews

Related threats