gaizhenbiao ChuanhuChatGPT filter_history keyword permissive regular expression
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in gaizhenbiao ChuanhuChatGPT and classified as critical. This affects the function filter_history. Such manipulation of the argument keyword leads to permissive regular expression.
This vulnerability is uniquely identified as CVE-2024-6038. The attack can be launched remotely. No exploit exists.
Details
A vulnerability was found in gaizhenbiao ChuanhuChatGPT (the affected version is unknown). It has been rated as critical. Affected by this issue is the function filter_history. The manipulation of the argument keyword with an unknown input leads to a permissive regular expression vulnerability. Using CWE to declare the problem leads to CWE-625. The product uses a regular expression that does not sufficiently restrict the set of allowed values. Impacted is availability. CVE summarizes:
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.
The advisory is available at huntr.com. This vulnerability is handled as CVE-2024-6038 since 06/15/2024. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details are known, but there is no available exploit.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.5VulDB Meta Temp Score: 7.3
VulDB Base Score: 7.5
VulDB Temp Score: 7.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 7.5
CNA Vector (huntr.dev): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Permissive regular expressionCWE: CWE-625 / CWE-185 / CWE-697
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
06/15/2024 🔍06/27/2024 🔍
06/27/2024 🔍
07/30/2025 🔍
Sources
Advisory: huntr.comStatus: Not defined
CVE: CVE-2024-6038 (🔍)
GCVE (CVE): GCVE-0-2024-6038
GCVE (VulDB): GCVE-100-269882
Entry
Created: 06/27/2024 21:31Updated: 07/30/2025 20:32
Changes: 06/27/2024 21:31 (61), 07/30/2025 20:32 (2)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.