Dropbear ignores permitopen limits 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 Full Disclosure post says a restricted key can reach docker.sock; the claim is tied to HEAD 99baf182.
A November 17 Full Disclosure post says Dropbear does not enforce permitopen and permitlisten restrictions for unix-socket forwarding. The author says a key limited to a named host and port can still forward to a unix socket, including docker.sock. The report cites HEAD 99baf182 and calls the issue live-proven. The feed text is cut off and does not name a CVE or a fix.
Unconfirmed: The live-proven claim is the poster's, and the snippet does not include a fix or CVE.
- Dropbear is described as the small SSH server used on embedded systems.
- permitopen and permitlisten are the restricted-key options involved.
- The cited revision is HEAD 99baf182.
Impact: Restricted SSH key can forward to unix sockets such as docker.sock
| Product | Affected |
|---|---|
| Dropbear | HEAD 99baf182 |
- 1.Review Dropbear keys that use permitopen or permitlisten before allowing unix-socket forwarding.
From the original article
Posted by theknell--- via Fulldisclosure on Nov 17 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.