{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-3404 exists.","fix":"No fix has been published for CVE-2024-3404 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-3404 is a medium-severity missing authorization vulnerability in gaizhenbiao/chuanhuchatgpt, published on 6 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-3404 and fix it if it is affected.\n\nWhat it is: CVE-2024-3404 is a medium-severity missing authorization vulnerability in gaizhenbiao/chuanhuchatgpt, published on 6 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-3404 exists.\n\nAffected product: gaizhenbiao/chuanhuchatgpt. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-3404/ (Markdown: https://insights.sbomify.com/CVE-2024-3404/index.md)","id":"CVE-2024-3404","markdown":"https://insights.sbomify.com/CVE-2024-3404/index.md","name":"CVE-2024-3404","record":{"aliases":["GHSA-3h92-xgh6-5m97"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"ChatGPT web application","requires_auth":"low_privilege","summary":"An authenticated attacker can bypass access controls to read other users' chat history files, exposing sensitive information.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntr_ai","cpe":[{"product":"chuanhuchatgpt","vendor":"gaizhenbiao"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Improper Access Control in gaizhenbiao/chuanhuchatgpt","id":"CVE-2024-3404","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"WP Prayer \u003c= 2.0.9 - Settings Update via CSRF","id":"CVE-2024-3405"},"packages":[],"prev":{"headline":"Local File Inclusion in imartinez/privategpt","id":"CVE-2024-3403"},"products":["gaizhenbiao/chuanhuchatgpt"],"published":"2024-06-06","related":[{"cvss_score":9.8,"headline":"Path Traversal in gaizhenbiao/chuanhuchatgpt","id":"CVE-2024-3234","kev_date_added":null,"published":"2024-06-06"},{"cvss_score":9.1,"headline":"Path Traversal in gaizhenbiao/chuanhuchatgpt","id":"CVE-2024-5982","kev_date_added":null,"published":"2024-10-29"},{"cvss_score":8.2,"headline":"Path Traversal in gaizhenbiao/chuanhuchatgpt","id":"CVE-2024-6255","kev_date_added":null,"published":"2024-07-31"},{"cvss_score":8.1,"headline":"Improper Access Control in gaizhenbiao/chuanhuchatgpt","id":"CVE-2024-8613","kev_date_added":null,"published":"2025-03-20"},{"cvss_score":8.1,"headline":"Authentication Bypass in gaizhenbiao/ChuanhuChatGPT","id":"CVE-2024-9216","kev_date_added":null,"published":"2025-03-20"},{"cvss_score":7.5,"headline":"Denial of Service (DoS) in gaizhenbiao/chuanhuchatgpt","id":"CVE-2024-10650","kev_date_added":null,"published":"2025-03-20"},{"cvss_score":7.5,"headline":"Denial of Service (DOS) in gaizhenbiao/chuanhuchatgpt","id":"CVE-2024-7807","kev_date_added":null,"published":"2024-10-29"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-10-15","vendors":["gaizhenbiao"]},"summary":"An authenticated attacker can bypass access controls to read other users' chat history files, exposing sensitive information.","url":"https://insights.sbomify.com/CVE-2024-3404/"}