# CVE-2024-2217: Improper Access Control in gaizhenbiao/chuanhuchatgpt

> Attackers can access config.json to steal API keys and credentials due to improper access control in the chuanhuchatgpt web application.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Apr 2024
- **Updated:** 22 Aug 2024
- **Also known as:** GHSA-5j77-g9r7-hpx3, PYSEC-2024-316

## What is CVE-2024-2217?

CVE-2024-2217 is a high-severity vulnerability in gaizhenbiao/chuanhuchatgpt, published on 10 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

gaizhenbiao/chuanhuchatgpt is vulnerable to improper access control, allowing unauthorized access to the `config.json` file. This vulnerability is present in both authenticated and unauthenticated versions of the application, enabling attackers to obtain sensitive information such as API keys (`openai_api_key`, `google_palm_api_key`, `xmchat_api_key`, etc.), configuration details, and user credentials. The issue stems from the application's handling of HTTP requests for the `config.json` file, which does not properly restrict access based on user authentication.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2024-2217?

1 open source package ship an affected version, including chuanhuchatgpt. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `chuanhuchatgpt` | PyPI | All versions to 20240121 | None |

Products: Gaizhenbiao Chuanhuchatgpt.

## How do I fix CVE-2024-2217?

No fix has been published for CVE-2024-2217 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-2217 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-2217 exists.

## Other vulnerabilities in gaizhenbiao/chuanhuchatgpt

- [CVE-2024-3234](https://insights.sbomify.com/CVE-2024-3234/): Path Traversal in gaizhenbiao/chuanhuchatgpt (critical 9.8)
- [CVE-2024-5982](https://insights.sbomify.com/CVE-2024-5982/): Path Traversal in gaizhenbiao/chuanhuchatgpt (critical 9.1)
- [CVE-2024-6255](https://insights.sbomify.com/CVE-2024-6255/): Path Traversal in gaizhenbiao/chuanhuchatgpt (high 8.2)
- [CVE-2024-8613](https://insights.sbomify.com/CVE-2024-8613/): Improper Access Control in gaizhenbiao/chuanhuchatgpt (high 8.1)
- [CVE-2024-9216](https://insights.sbomify.com/CVE-2024-9216/): Authentication Bypass in gaizhenbiao/ChuanhuChatGPT (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-2217 and fix it if it is affected.

What it is: CVE-2024-2217 is a high-severity vulnerability in gaizhenbiao/chuanhuchatgpt, published on 10 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-2217 exists.

Affected packages and fixed versions:
- chuanhuchatgpt (PyPI): affected all versions up to 20240121; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-2217/ (Markdown: https://insights.sbomify.com/CVE-2024-2217/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-2217
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-2217
- OSV: https://osv.dev/vulnerability/CVE-2024-2217

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-2217/
Summaries are generated and may contain mistakes; the official description above is the record.