gaizhenbiao chuanhuchatgpt History File access control

Summaryinfo

A vulnerability was found in gaizhenbiao chuanhuchatgpt. It has been rated as critical. This issue affects some unknown processing of the component History File Handler. This manipulation causes access control. This vulnerability is tracked as CVE-2024-3404. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability classified as critical was found in gaizhenbiao chuanhuchatgpt (version unknown). Affected by this vulnerability is an unknown function of the component History File Handler. The manipulation with an unknown input leads to a access control vulnerability. The CWE definition for the vulnerability is CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. As an impact it is known to affect confidentiality. The summary by CVE is:

In gaizhenbiao/chuanhuchatgpt, specifically the version tagged as 20240121, there exists a vulnerability due to improper access control mechanisms. This flaw allows an authenticated attacker to bypass intended access restrictions and read the `history` files of other users, potentially leading to unauthorized access to sensitive information. The vulnerability is present in the application's handling of access control for the `history` path, where no adequate mechanism is in place to prevent an authenticated user from accessing another user's chat history files. This issue poses a significant risk as it could allow attackers to obtain sensitive information from the chat history of other users.

The advisory is shared at huntr.com. This vulnerability is known as CVE-2024-3404 since 04/05/2024. The exploitation appears to be easy. The attack can be launched remotely. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 09/24/2024). MITRE ATT&CK project uses the attack technique T1068 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• gaizhenbiao

Name

• chuanhuchatgpt

CPE 2.3info

• 🔍

CPE 2.2info

• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion