Summary
The Chisel server doesn't ever read the documented AUTH environment variable used to set credentials, which allows any unauthenticated user to connect, even if credentials were set. This advisory is a formalization of a report sent to the maintainer via email.
Details
In the help page for the chisel server subcommand, it mentions an AUTH environment variable that can be set in order to provide credentials that the server should authenticate connections against:
|
authfile with {"<user:pass>": [""]}. If unset, it will use the |
.
The issue is that the server entrypoint doesn't ever read the AUTH environment variable. The only place that this happens is in the client entrypoint:
|
config.Auth = os.Getenv("AUTH") |
This subverts the expectations set by the documentation, allowing unauthenticated users to connect to a Chisel server, even if auth is attempted to be set up in this manner.
PoC
Run chisel server, first specifying credentials with the AUTH environment variable, then with the --auth argument. In the first case, the server allows connections without authentication, while in the second, the correct behavior is exhibited.
Impact
Anyone who is running the Chisel server, and that is using the AUTH environment variable to specify credentials to authenticate against. Chisel is often used to provide an entrypoint to a private network, which means services that are gated by Chisel may be affected. Additionally, Chisel is often used for exposing services to the internet. An attacker could MITM requests by connecting to a Chisel server and requesting to forward traffic from a remote port.
lleyton Reporter
korewaChino Finder
jpillora Remediation developer
Summary
The Chisel server doesn't ever read the documented
AUTHenvironment variable used to set credentials, which allows any unauthenticated user to connect, even if credentials were set. This advisory is a formalization of a report sent to the maintainer via email.Details
In the help page for the
chisel serversubcommand, it mentions anAUTHenvironment variable that can be set in order to provide credentials that the server should authenticate connections against:chisel/main.go
Line 138 in 3de1774
The issue is that the server entrypoint doesn't ever read the
AUTHenvironment variable. The only place that this happens is in the client entrypoint:chisel/main.go
Line 452 in 3de1774
This subverts the expectations set by the documentation, allowing unauthenticated users to connect to a Chisel server, even if auth is attempted to be set up in this manner.
PoC
Run
chisel server, first specifying credentials with theAUTHenvironment variable, then with the--authargument. In the first case, the server allows connections without authentication, while in the second, the correct behavior is exhibited.Impact
Anyone who is running the Chisel server, and that is using the
AUTHenvironment variable to specify credentials to authenticate against. Chisel is often used to provide an entrypoint to a private network, which means services that are gated by Chisel may be affected. Additionally, Chisel is often used for exposing services to the internet. An attacker could MITM requests by connecting to a Chisel server and requesting to forward traffic from a remote port.