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-8955: CWE-918 Server-Side Request Forgery (SSRF) in composiohq composiohq/composio

0
Medium
VulnerabilityCVE-2024-8955cvecve-2024-8955cwe-918
Published: Thu Mar 20 2025 (03/20/2025, 10:09:27 UTC)
Source: CVE Database V5
Vendor/Project: composiohq
Product: composiohq/composio

Description

A Server-Side Request Forgery (SSRF) vulnerability exists in composiohq/composio version v0.4.4. This vulnerability allows an attacker to read the contents of any file in the system by exploiting the BROWSERTOOL_GOTO_PAGE and BROWSERTOOL_GET_PAGE_DETAILS actions.

AI-Powered Analysis

AILast updated: 10/15/2025, 13:19:47 UTC

Technical Analysis

CVE-2024-8955 is a Server-Side Request Forgery (SSRF) vulnerability classified under CWE-918, affecting composiohq/composio version v0.4.4. SSRF vulnerabilities occur when an attacker can manipulate a server to make HTTP requests to unintended locations, often internal resources or local files. In this case, the vulnerability allows an attacker to exploit the BROWSERTOOL_GOTO_PAGE and BROWSERTOOL_GET_PAGE_DETAILS actions to read arbitrary files on the server's filesystem. This is significant because it can lead to unauthorized disclosure of sensitive information stored on the server, such as configuration files, credentials, or other private data. The vulnerability requires the attacker to have high privileges (authenticated access with elevated rights), and no user interaction is needed, which means exploitation can be automated once access is obtained. The CVSS v3.0 score is 6.8, reflecting a medium severity level, with a vector indicating network attack vector, low attack complexity, high privileges required, no user interaction, and a scope change with high confidentiality impact but no integrity or availability impact. No patches or exploit code are currently publicly available, and no known exploits in the wild have been reported. However, the vulnerability poses a risk of sensitive data exposure if exploited. Organizations using composiohq/composio should assess their exposure, restrict access to the affected functionality, and monitor for suspicious activity.

Potential Impact

For European organizations, the primary impact of CVE-2024-8955 is the potential unauthorized disclosure of sensitive internal files, which can include credentials, configuration data, or intellectual property. This can lead to further compromise if attackers leverage disclosed information to escalate privileges or move laterally within networks. The requirement for high privileges limits the attack surface to insiders or attackers who have already breached initial defenses, but the lack of need for user interaction facilitates automated exploitation. Confidentiality breaches can have regulatory implications under GDPR, especially if personal or sensitive data is exposed. The vulnerability does not directly affect system integrity or availability, but the indirect consequences of data leakage could be severe, including reputational damage and compliance penalties. Organizations in sectors such as finance, healthcare, government, and critical infrastructure that use composiohq/composio are particularly at risk due to the sensitivity of their data and regulatory environment.

Mitigation Recommendations

1. Immediately restrict access to the BROWSERTOOL_GOTO_PAGE and BROWSERTOOL_GET_PAGE_DETAILS functionalities to only trusted and necessary users. 2. Implement strict authentication and authorization controls to ensure only users with legitimate high privileges can access these features. 3. Monitor logs for unusual or unauthorized access patterns involving these actions. 4. If possible, isolate the composiohq/composio deployment within a segmented network zone to limit exposure. 5. Employ web application firewalls (WAFs) with custom rules to detect and block SSRF attack patterns targeting these endpoints. 6. Since no official patch is currently available, consider applying virtual patching or disabling the vulnerable features temporarily until a vendor patch is released. 7. Conduct thorough code review and penetration testing focused on SSRF vectors in the application. 8. Educate administrators and users about the risks and signs of SSRF exploitation. 9. Plan for rapid deployment of vendor patches once released and maintain up-to-date inventories of affected software versions.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
@huntr_ai
Date Reserved
2024-09-17T18:24:07.208Z
Cvss Version
3.0
State
PUBLISHED

Threat ID: 68ef9b2e178f764e1f470e8e

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

Last enriched: 10/15/2025, 1:19:47 PM

Last updated: 12/3/2025, 3:22:03 PM

Views: 31

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