Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2024-9311: CWE-352 Cross-Site Request Forgery (CSRF) in haotian-liu haotian-liu/llava

0
Medium
VulnerabilityCVE-2024-9311cvecve-2024-9311cwe-352
Published: Thu Mar 20 2025 (03/20/2025, 10:10:24 UTC)
Source: CVE Database V5
Vendor/Project: haotian-liu
Product: haotian-liu/llava

Description

A Cross-Site Request Forgery (CSRF) vulnerability in haotian-liu/llava v1.2.0 (LLaVA-1.6) allows an attacker to upload files with malicious content without authentication or user interaction. The uploaded file is stored in a predictable path, enabling the attacker to execute arbitrary JavaScript code in the context of the victim's browser by visiting the crafted file URL. This can lead to theft of sensitive information, session hijacking, or other actions compromising the security and privacy of the victim.

AI-Powered Analysis

AILast updated: 10/15/2025, 13:06:23 UTC

Technical Analysis

CVE-2024-9311 is a CSRF vulnerability identified in haotian-liu/llava version 1.2.0 (LLaVA-1.6). This vulnerability allows an unauthenticated attacker to upload files containing malicious JavaScript code without any user interaction or authentication. The files are stored in predictable paths on the server, which means an attacker can craft URLs pointing to these malicious files. When a victim visits such a URL, the embedded JavaScript executes in the context of the victim's browser, potentially leading to session hijacking, theft of sensitive information, or other malicious actions compromising confidentiality and privacy. The vulnerability exploits the lack of CSRF protections on the file upload functionality, allowing cross-origin requests to perform unauthorized actions. The CVSS 3.0 base score is 6.1, reflecting medium severity due to network attack vector, no privileges required, but requiring user interaction. The vulnerability affects all unspecified versions of haotian-liu/llava, and no patches or known exploits are currently published. The predictable storage path of uploaded files increases the risk by simplifying exploitation. This vulnerability falls under CWE-352, which covers CSRF issues where state-changing requests can be forged by attackers.

Potential Impact

For European organizations using haotian-liu/llava, this vulnerability poses a significant risk to client-side security and user privacy. Attackers can exploit this flaw to execute arbitrary JavaScript in users' browsers, potentially leading to session hijacking, unauthorized access to sensitive data, and compromise of user accounts. This can result in data breaches, loss of trust, and regulatory non-compliance under GDPR due to exposure of personal data. Since the attack requires victims to visit malicious URLs, phishing campaigns or malicious links could be used to trigger exploitation. The predictable file storage path increases the likelihood of successful attacks. Organizations relying on this software for AI or machine learning workloads that involve user interaction or web interfaces are particularly at risk. The medium severity score indicates a moderate but actionable threat that should be addressed promptly to avoid escalation.

Mitigation Recommendations

1. Implement CSRF protections such as anti-CSRF tokens on all state-changing endpoints, especially file upload functionality. 2. Restrict file upload permissions and validate file types and contents rigorously to prevent malicious scripts. 3. Use unpredictable, randomized file storage paths or filenames to reduce the risk of attackers guessing URLs. 4. Employ Content Security Policy (CSP) headers to limit the execution of unauthorized scripts in browsers. 5. Educate users to avoid clicking on suspicious links and implement email filtering to reduce phishing risks. 6. Monitor web server logs for unusual file uploads or access patterns indicating exploitation attempts. 7. Apply the latest patches or updates from the vendor once available. 8. If immediate patching is not possible, consider isolating the vulnerable service or restricting access to trusted networks. 9. Conduct regular security assessments and penetration testing focusing on CSRF and file upload vectors. 10. Implement multi-factor authentication to reduce the impact of session hijacking if it occurs.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
@huntr_ai
Date Reserved
2024-09-27T22:47:19.228Z
Cvss Version
3.0
State
PUBLISHED

Threat ID: 68ef9b2f178f764e1f470edf

Added to database: 10/15/2025, 1:01:35 PM

Last enriched: 10/15/2025, 1:06:23 PM

Last updated: 12/3/2025, 1:50:17 AM

Views: 33

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats