CVE-2025-56427

7.5 HIGH

📋 TL;DR

A directory traversal vulnerability in ComposioHQ v0.7.20 allows remote attackers to access sensitive files outside the intended directory via the _download_file_or_dir function. This affects all deployments running the vulnerable version, potentially exposing configuration files, credentials, or other sensitive data.

💻 Affected Systems

Products:
  • ComposioHQ
Versions: v0.7.20
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: All deployments using the vulnerable version are affected regardless of configuration.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete system compromise through exposure of SSH keys, database credentials, configuration files with secrets, or other critical system files leading to lateral movement or data exfiltration.

🟠

Likely Case

Exposure of application configuration files, API keys, tokens, or user data stored in accessible directories, potentially enabling further attacks or data breaches.

🟢

If Mitigated

Limited exposure of non-critical files if proper file permissions and directory restrictions are in place, with minimal impact on overall system security.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Public proof-of-concept demonstrates exploitation via crafted path traversal sequences in API requests.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: Unknown

Restart Required: Yes

Instructions:

1. Monitor official ComposioHQ channels for security updates. 2. Upgrade to a patched version when available. 3. Restart the ComposioHQ service after patching.

🔧 Temporary Workarounds

Input Validation and Sanitization

all

Implement strict input validation to reject path traversal sequences (../, ..\) in file download requests.

# Modify the _download_file_or_dir function to validate and sanitize input paths
# Example Python snippet: if '..' in requested_path: return error

Web Application Firewall Rules

all

Configure WAF to block requests containing directory traversal patterns targeting the vulnerable endpoint.

# Example WAF rule to block ../ patterns
SecRule ARGS "\.\./" "id:1001,phase:2,deny,status:403,msg:'Directory Traversal Attempt'

🧯 If You Can't Patch

  • Restrict network access to the ComposioHQ service using firewall rules to only allow trusted IP addresses.
  • Implement strict file system permissions to limit the directories accessible to the ComposioHQ process.

🔍 How to Verify

Check if Vulnerable:

Test by sending a request to the vulnerable endpoint with a path traversal payload (e.g., /api/download?file=../../etc/passwd) and checking if restricted files are returned.

Check Version:

Check the version in the ComposioHQ configuration or via the application's admin interface.

Verify Fix Applied:

After applying mitigations, repeat the test with traversal payloads and verify that requests are blocked or return appropriate error messages.

📡 Detection & Monitoring

Log Indicators:

  • HTTP requests containing ../ or ..\ patterns
  • Unusual file access patterns from the ComposioHQ process
  • 403 or 400 errors indicating blocked traversal attempts

Network Indicators:

  • HTTP requests with encoded traversal sequences (%2e%2e%2f)
  • Multiple failed attempts to access restricted paths

SIEM Query:

source="composio.log" AND ("../" OR "..\\" OR "%2e%2e%2f")

🔗 References

📤 Share & Export