CVE-2024-3234 is a critical severity (CVSS 9.8) path traversal in the gaizhenbiao ChuanhuChatGPT application, caused by an outdated gradio component. Unauthorized users could read sensitive files such as config.json, which holds API keys. The fix is the release dated 20240305 or later, and keys should be rotated.
What's affected
The ChuanhuChatGPT application, in versions before the fixed version released on 20240305. The record says the issue affects the latest version prior to that fixed version, and links the fix commit on GitHub and a huntr report. The cause is the gradio component bundled with the application, which is affected by CVE-2023-51449, a path traversal in gradio.
The application is meant to restrict user access to its web_assets folder. With the old gradio, that restriction could be bypassed, giving access to files such as config.json. The huntr page we tried to retrieve did not return report content, so we rely on the record for the details.
Because the project does not appear to use semantic version numbers in the record, identify your build by its date or commit.
The weakness class: CWE-22, path traversal. The NVD record scores it 9.8 (critical) with the vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. CISA Known Exploited Vulnerabilities status in the record: not listed.
How to check if you're exposed
Check how your deployment was installed. For a git checkout:
git log -1 --format=%cd
pip show gradio
If your checkout predates 5 March 2024, or the installed gradio is the old version flagged for CVE-2023-51449, you are likely affected. For Docker images, check the image build date and its gradio version.
What to do now
- Update ChuanhuChatGPT to the build released on 20240305 or later and update gradio to a fixed release.
- Rotate every API key that was stored in config.json on any internet reachable instance.
- Put the application behind authentication and do not expose it directly to the internet.
- Review access logs for requests to the asset path with parent directory sequences.
Why it matters
Path traversal, CWE-22, here arrives through a dependency. The application authors wrote a restriction, but the framework underneath did not enforce it. That is the supply chain lesson: a flaw in a transitive component becomes your flaw once you ship it.
The damage is credential exposure. A config file with model provider keys can be spent by whoever reads it, so rotation matters as much as patching. Reachability analysis helps decide which of your services actually serve files through the vulnerable gradio path.
Try it yourself
Click through it at your own pace, or open it full screen.
Quick check
Why does a gradio CVE show up as a ChuanhuChatGPT CVE?
The application bundles gradio, and the old gradio has a path traversal tracked as CVE-2023-51449. The record assigns a separate CVE to the application because it shipped the vulnerable component and exposed config.json through it.
Sources
- Fix commit on GitHub (listed in the record, not individually reviewed)
- huntr report (listed in the record; our fetch returned no report content)
- Safeguard Gold entry for CVE-2024-3234
- Free in-browser dependency scan
Last reviewed: 19 October 2026.
