CVE-2024-8143
Gaizhenbiao Chuanhuchatgpt 2024-06-28
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2024-8143 is a medium-severity Data Access Operations Outside of Expected Data Manager Component (CWE-1057) vulnerability in Gaizhenbiao Chuanhuchatgpt. Its CVSS base score is 4.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Direct Volume Access (T1006); ranked at the 40th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
This vulnerability is AI-related — categorised as LLM Application Platforms; in the Privacy and Disclosure risk domain.
The strongest mitigations our analysis identified map to AC-25 (Reference Monitor) and AC-3 (Access Enforcement) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-0023
Vulnerability Data
In the latest version (20240628) of gaizhenbiao/chuanhuchatgpt, an issue exists in the /file endpoint that allows authenticated users to access the chat history of other users. When a user logs in, a directory is created in the history folder with…
more
the user's name. By manipulating the /file endpoint, an authenticated user can enumerate and access files in other users' directories, leading to unauthorized access to private chat histories. This vulnerability can be exploited to read any user's private chat history.
- CWE(s)
AI Security AnalysisAI
- AI Category
- LLM Application Platforms
- Risk Domain
- Privacy and Disclosure
- OWASP Top 10 for LLMs 2025
- None mapped
- Classification Reason
- ChuanHuChatGPT is a web-based chat interface and platform for interacting with LLMs like ChatGPT, fitting the Enterprise AI Assistants category as it provides user-facing AI chat functionality with history management.
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V7.2.1
Mitigating Controls (NIST 800-53 r5) AI
Requires a tamperproof, always-invoked reference monitor that forces every data access through the designated manager.
Enforces all data access through approved, centralized mechanisms rather than allowing ad-hoc bypasses.
Mandates security engineering principles such as centralized mediation and least privilege during design, preventing bypass code from being written.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly enforce use of the designated data manager component for all access paths.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect unauthorized data-access paths bypassing the central manager.
Secure SDLC mandates use of approved data-access components and prevents ad-hoc direct access.
Application security requirements can specify central data-manager usage, mitigating the weakness.
Secure architecture principles require all data operations to flow through the designated manager component.
Secure coding standards prohibit direct data access outside the approved data-manager abstraction.
Enforces data-access restrictions through defined interfaces, reducing bypass of the central data manager.