| Package | Affected versions | Patched versions |
|---|---|---|
| github.com/hydraide/hydraide | ≥ 2.1.1, < 2.2.1< 0.0.0-20250816184905-1256db38c33c | 2.2.10.0.0-20250816184905-1256db38c33c |
There is no authentication of any kind.
TLS is implemented, the tunnel between the client and server is secure, however once data is on the server, it's free to be read by any adversaries.
On the client side : https://github.com/hydraide/hydraide/blob/main/sdk/go/hydraidego/client/client.go#L221 It should be using a TLS Config with RootCAs and Certificates, currently RootCAs only (under NewClientTLSFromFile)
And on the server side, there should be ClientCAs and ClientAuth filled.
To bypass as is, the simplest way is to take the client and modify the code as such :
Modified from https://github.com/hydraide/hydraide/blob/main/sdk/go/hydraidego/client/client.go#L209
// hostOnly := strings.Split(server.Host, ":")[0]
// creds, certErr := credentials.NewClientTLSFromFile(server.CertFilePath, hostOnly)
// if certErr != nil {
// slog.Error("error while loading TLS credentials: ", "error", certErr, "server", server.Host, "fromIsland", server.FromIsland, "toIsland", server.ToIsland)
// errorMessages = append(errorMessages, certErr)
// }
var opts []grpc.DialOption
tlsConfig := &tls.Config{
InsecureSkipVerify: true,
}
creds := credentials.NewTLS(tlsConfig)
opts = append(opts, grpc.WithTransportCredentials(creds))
It impacts everyone who think there is any kind of authentication.
This vulnerability has been fully fixed in server/v2.2.1 together with hydraidectl/v0.2.1.
All users are strongly advised to upgrade:
For migration help, join the community Discord: https://discord.gg/xE2YSkzFRm or open a GitHub Discussion. If anything does not work, please report it.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free