GHSA-7h8w-hj9j-8rjw
HIGHOpenHands is Vulnerable to Command Injection through its Git Diff Handler
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
openhands-aiReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
Summary
A Command Injection vulnerability exists in the get_git_diff() method at openhands/runtime/utils/git_handler.py:134. The path parameter from the /api/conversations/{conversation_id}/git/diff API endpoint is passed unsanitized to a shell command, allowing authenticated attackers to execute arbitrary commands in the agent sandbox. The user is already allowed to instruct the agent to execute commands, but this bypasses the normal channels.
Details
Vulnerable Code Path
The vulnerability flows through these files:
- API Endpoint (
openhands/server/routes/files.py:267-277)
@app.get('/git/diff')
async def git_diff(
path: str, # <-- User input from HTTP request
...
):
...
diff = await call_sync_from_async(runtime.get_git_diff, path, cwd) # No sanitization
- Runtime (
openhands/runtime/base.py:1231-1233)
def get_git_diff(self, file_path: str, cwd: str) -> dict[str, str]:
self.git_handler.set_cwd(cwd)
return self.git_handler.get_git_diff(file_path) # Passed directly
- Vulnerable Method (
openhands/runtime/utils/git_handler.py:10-12, 134)
# Command template with placeholder
GIT_DIFF_CMD = 'python3 /openhands/code/openhands/runtime/utils/git_diff.py "{file_path}"'
# Line 134 - VULNERABLE: User input directly interpolated
result = self.execute(self.git_diff_cmd.format(file_path=file_path), self.cwd)
- Shell Execution (
openhands/runtime/utils/git_diff.py:25-27)
def run(cmd: str, cwd: str) -> str:
result = subprocess.run(
args=cmd,
shell=True, # <-- Enables shell metacharacter interpretation
stdout=subprocess.PIPE,
stderr=subprocess.PIPE,
cwd=cwd
)
Root Cause
The file_path parameter is directly interpolated into a shell command string using Python's .format() method without any sanitization. When this command is executed with shell=True, shell metacharacters like ", ;, and # are interpreted, allowing command injection.
Example:
- Input:
test"; id # - Constructed command:
python3 /script.py "test"; id #" - Shell interprets as two commands:
python3 /script.py "test"ANDid
Impact
Who is Affected
- All OpenHands deployments exposing the
/api/conversations/{id}/git/diffendpoint - Any authenticated user can exploit this vulnerability,
Attack Capabilities
An attacker can:
- Execute arbitrary commands on the runtime container as root
- Read sensitive files including
.env, API keys, source code - Write arbitrary files to inject malicious code
- Establish reverse shells for persistent access
- Potentially escape the container if Docker is misconfigured
Mitigation
Users should update to the latest version of OpenHands that includes the changes from PR #13051. The fix replaces direct shell string formatting with proper argument array handling or rigorous path sanitization to prevent command chaining.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | openhands-ai | all versions | 1.5.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openhands-ai. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update openhands-ai to 1.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7h8w-hj9j-8rjw is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-7h8w-hj9j-8rjw is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-7h8w-hj9j-8rjw. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-7h8w-hj9j-8rjw in your dependencies?
O3 detects GHSA-7h8w-hj9j-8rjw across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.