Dropbear skips permitopen and permitlisten on unix-socket forwarding
Original title: Dropbear: the restriction names an address — permitopen/permitlisten not enforced for unix-socket forwarding, docker.sock reachable (HEAD 99baf182, live-proven)
A restricted SSH key can still reach unix sockets such as docker.sock; shown on HEAD 99baf182.
An oss-security post says Dropbear, the small SSH server used on routers, embedded systems and appliances, does not enforce permitopen and permitlisten when forwarding to unix sockets. Those authorized_keys options are meant to limit a key to a named host and port. The reporter says docker.sock is reachable and the issue was live-proven on HEAD 99baf182. No fixed release or CVE is named in the snippet.
Unconfirmed: The post is truncated, so the full affected range and any fix are not stated.
- The bug concerns unix-socket forwarding, not host:port checks.
- docker.sock is cited as reachable through a restricted key.
- The report names HEAD commit 99baf182.
- No patch version or CVE appears in the snippet.
Impact: restricted key can reach unix sockets such as docker.sock
| Product | Affected |
|---|---|
| Dropbear | HEAD 99baf182 |
From the original article
Posted by theknell on Nov 13 Dropbear is the SSH server that ships where OpenSSH is too big: routers, embedded systems, rescue images, appliances — anywhere a small, hardened sshd is wanted. It has been fuzzed and audited for two decades, and its handling of restricted keys is one of the reasons administrators trust it with narrow jobs.
seclists.org
A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.