CVE-2024-5820
Published: 27 June 2024
Summary
CVE-2024-5820 is a high-severity Missing Authorization (CWE-862) vulnerability in Stitionai Devika. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 28.0th 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 Enterprise AI Assistants; in the Protocol-Specific Risks risk domain; MITRE ATLAS techniques in scope: AML.T0040.000, Direct (AML.T0051.000).
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-46968
Vulnerability details
An unprotected WebSocket connection in the latest version of stitionai/devika (commit ecee79f) allows a malicious website to connect to the backend and issue commands on behalf of the user. The backend serves all listeners on the given socket, enabling any…
more
such malicious website to intercept all communication between the user and the backend. This vulnerability can lead to unauthorized command execution and potential server-side request forgery.
- CWE(s)
AI Security AnalysisAI
- AI Category
- Enterprise AI Assistants
- Risk Domain
- Protocol-Specific Risks
- OWASP Top 10 for LLMs 2025
- None mapped
- Classification Reason
- stitionai/devika is an open-source AI coding agent/assistant (similar to AI software engineers), fitting the Enterprise AI Assistants category. The vulnerability involves an unprotected WebSocket in its backend, confirming AI-related impact as reported on an AI/ML bug bounty platform.
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
Unprotected WebSocket in public-facing backend enables exploitation (T1190) for unauthorized command execution (T1059) and SSRF.
MITRE ATLAS TechniquesAI
MITRE ATLAS techniques
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Requiring an access control policy ensures authorization checks are defined and applied for critical functions.
Reviews of access controls detect missing authorization checks on critical functions or resources.
Documenting permitted unauthenticated actions prevents missing authorization by making all exceptions explicit and subject to organizational review.
Requiring attribute association with information prevents authorization from being performed without necessary security or privacy context.
Mandating authorization prior to allowing remote connections addresses missing authorization for remote access.
Mandating authorization before wireless connections are allowed prevents missing authorization for wireless access.
The control requires authorization before allowing mobile device connections, directly mitigating missing authorization for system access.
Requiring approvals for account creation and specifying authorizations ensures authorization is not missing for system access.