CVE-2025-61492

10.0 CRITICAL

📋 TL;DR

A command injection vulnerability in terminal-controller-mcp 0.1.7 allows attackers to execute arbitrary system commands by providing malicious input to the execute_command function. This affects any system running the vulnerable version of this terminal controller package, potentially giving attackers full control of the affected system.

💻 Affected Systems

Products:
  • terminal-controller-mcp
Versions: 0.1.7
Operating Systems: All platforms where terminal-controller-mcp runs
Default Config Vulnerable: ⚠️ Yes
Notes: The vulnerability exists in the execute_command function which appears to be a core component of the package.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete system compromise allowing attackers to execute arbitrary commands with the privileges of the running process, potentially leading to data theft, ransomware deployment, or lateral movement within the network.

🟠

Likely Case

Remote code execution leading to unauthorized access, data exfiltration, or installation of backdoors on affected systems.

🟢

If Mitigated

Limited impact if proper input validation and command sanitization are implemented, restricting attackers to specific allowed commands only.

🌐 Internet-Facing: HIGH - If the vulnerable component is exposed to the internet, attackers can remotely exploit it without authentication.
🏢 Internal Only: HIGH - Even internally, any user or service that can interact with the vulnerable function can achieve command execution.

🎯 Exploit Status

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

Command injection vulnerabilities are typically easy to exploit once the attack vector is identified. The GitHub issues suggest the vulnerability is known and may have exploit code available.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: None available

Restart Required: No

Instructions:

1. Check the GitHub repository for updates
2. If a patched version is available, update terminal-controller-mcp
3. Review and test the update before deploying to production

🔧 Temporary Workarounds

Input Validation and Sanitization

all

Implement strict input validation and command sanitization before passing user input to execute_command

Implement input validation in your application code before calling execute_command

Restrict Command Execution

all

Limit the commands that can be executed through the vulnerable function

Implement allow-listing of permitted commands in your application

🧯 If You Can't Patch

  • Isolate affected systems from critical networks and internet access
  • Implement strict network segmentation and firewall rules to limit access to the vulnerable service

🔍 How to Verify

Check if Vulnerable:

Check if terminal-controller-mcp version 0.1.7 is installed in your environment

Check Version:

npm list terminal-controller-mcp

Verify Fix Applied:

Verify that terminal-controller-mcp has been updated to a version later than 0.1.7 or removed

📡 Detection & Monitoring

Log Indicators:

  • Unusual command execution patterns
  • Commands with shell metacharacters (;, &, |, $)
  • Commands from unexpected sources

Network Indicators:

  • Unexpected outbound connections from systems running terminal-controller-mcp
  • Suspicious payloads in API requests to the vulnerable endpoint

SIEM Query:

source="application_logs" AND (process="terminal-controller-mcp" OR message="execute_command") AND (command CONTAINS ";" OR command CONTAINS "&" OR command CONTAINS "|")

🔗 References

📤 Share & Export