Security Digest · Critical advisory (no CVE assigned)
GHSA-qp7j-x725-g67f: HydrAIDE Authentication Bypass Vulnerability
Summary There is no authentication of any kind.
CVSS 10.0 Critical GitHub-reviewed · critical
Should you act?
- Only if you depend on one of the packages below, directly or transitively, in a vulnerable version. Check your lockfile with
govulncheck ./.... - No CVE has been assigned, so it will not appear in CVE-based scanners that ignore GitHub advisories.
npm audit,pip-auditand Dependabot do read GitHub advisories.
Affected packages
| Ecosystem | Package | Vulnerable | First fixed |
|---|---|---|---|
| Go | github.com/hydraide/hydraide | >= 2.1.1, < 2.2.1 | 2.2.1 |
| Go | github.com/hydraide/hydraide | < 0.0.0-20250816184905-1256db38c33c | 0.0.0-20250816184905-1256db38c33c |
Details
Summary There is no authentication of any kind.
Details 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.
PoC 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
Impact It impacts everyone who think there is any kind of authentication.
---
CVSS: 10.0 (v3.1) CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Sources and references
- GitHub Advisory GHSA-qp7j-x725-g67f github.com
- github.com github.com
- github.com github.com
- pkg.go.dev pkg.go.dev