CVE-2024-5822 json
Server-Side Request Forgery (SSRF) in gaizhenbiao/ChuanhuChatGPT
published 2y ago modified 4mo ago also PYSEC-2024-268 , EUVD-2024-46970
- cvss
- 7.3
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 44%
- public exploits
- 0
- none known
Summary
A Server-Side Request Forgery (SSRF) vulnerability exists in the upload processing interface of gaizhenbiao/ChuanhuChatGPT versions <= ChuanhuChatGPT-20240410-git.zip. This vulnerability allows attackers to send crafted requests from the vulnerable server to internal or external resources, potentially bypassing security controls and accessing sensitive data.
Is CVE-2024-5822 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 2y ago
Exploit prediction
0.52% chance of exploitation in the next 30 days, higher than 44% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- huntr.com https://huntr.com/bounties/b24f1b5f-a529-435b-ac4d-5ca71d5d1fb5 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 7.3 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| OSV | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | chuanhuchatgpt | <=20240410 |
no fix listed |
Affected products
- gaizhenbiao gaizhenbiao/chuanhuchatgpt
- gaizhenbiao chuanhuchatgpt
Classification
- Weakness
-
- CWE-918 Server-Side Request Forgery
References
-
huntr.com
/bounties/b24f1b5f-a529-435b-ac4d-5ca71d5d1fb5
exploit, third-party-advisory, evidence
Sources
- CVE List CVE-2024-5822
- NVD CVE-2024-5822
- OSV PYSEC-2024-268
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.