gaizhenbiao ChuanhuChatGPT get_model critical step in authentication
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in gaizhenbiao ChuanhuChatGPT. It has been classified as critical. Affected by this vulnerability is the function get_model. Performing a manipulation results in critical step in authentication.
This vulnerability was named CVE-2024-9216. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability, which was classified as critical, was found in gaizhenbiao ChuanhuChatGPT (unknown version). This affects the function get_model. The manipulation with an unknown input leads to a critical step in authentication vulnerability. CWE is classifying the issue as CWE-304. The product implements an authentication technique, but it skips a step that weakens the technique. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
An authentication bypass vulnerability exists in gaizhenbiao/ChuanhuChatGPT, as of commit 3856d4f, allowing any user to read and delete other users' chat history. The vulnerability arises because the username is provided via an HTTP request from the client side, rather than being read from a secure source like a cookie. This allows an attacker to pass another user's username to the get_model function, thereby gaining unauthorized access to that user's chat history.
The advisory is shared at huntr.com. This vulnerability is uniquely identified as CVE-2024-9216 since 09/26/2024. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details are known, but no exploit is available.
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 the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.2VulDB Meta Temp Score: 7.1
VulDB Base Score: 6.3
VulDB Temp Score: 6.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 8.1
CNA Vector (@huntr_ai): 🔍
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: Critical step in authenticationCWE: CWE-304
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
09/26/2024 🔍03/20/2025 🔍
03/20/2025 🔍
08/01/2025 🔍
Sources
Advisory: huntr.comStatus: Not defined
CVE: CVE-2024-9216 (🔍)
GCVE (CVE): GCVE-0-2024-9216
GCVE (VulDB): GCVE-100-300333
Entry
Created: 03/20/2025 14:33Updated: 08/01/2025 21:32
Changes: 03/20/2025 14:33 (60), 08/01/2025 21:32 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.