OpenHands / OpenHands/software-agent-sdk

Security: requesting a private disclosure channel

Open
#5,034 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

documentation question security
Dominant language
Python
Stars
1.1k
Forks
539
Avg merge
1d 19h
Merged PRs (30d)
137

Description

Hi maintainers,

We found what we believe is a security-relevant issue in the default configuration of DockerWorkspace/DockerDevWorkspace (the documented sandbox launcher). We'd like to report it responsibly rather than posting full details in a public issue.

This repository doesn't currently have GitHub's private vulnerability reporting enabled and has no SECURITY.md. Could you either enable private vulnerability reporting (Settings -> Security -> Enable), or point us to a security contact email? Happy to share the full technical writeup as soon as there's a private channel available.

Actual Behavior

Running the SDK's own documented example for a Docker-sandboxed agent server, using its default configuration with no extra setup, results in the agent server being reachable over the network with no authentication required for its request-execution API. We believe this affects the standard DockerWorkspace/DockerDevWorkspace launch path, not a misconfiguration on our end.

Acceptance Criteria
  • Maintainers confirm a private channel (GitHub PVR or a security contact email) so we can share full reproduction steps and the affected code paths.
  • Default configuration is reviewed so an agent server started via the documented example does not expose an unauthenticated network-reachable execution API.

Thanks!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the documented Docker-sandboxed agent server example and the default DockerWorkspace/DockerDevWorkspace launch paths. First establish a private disclosure channel for the withheld reproduction details; done means maintainers can review the affected code paths and confirm that the default example does not expose an unauthenticated network-reachable execution API.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, python
Domain
backend-api-design, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.