# GHSA-qp7j-x725-g67f: HydrAIDE Authentication Bypass Vulnerability

> HydrAIDE lacks authentication, allowing attackers to read server data without credentials. Users must upgrade to secure versions.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Aug 2025
- **Also known as:** GO-2025-3895

## What is GHSA-qp7j-x725-g67f?

GHSA-qp7j-x725-g67f is an authentication bypass vulnerability in github.com/hydraide/hydraide, published on 19 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

### 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
```go
			// 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))
```

### Impact
It impacts everyone who think there is any kind of authentication.

---

## Resolution

This vulnerability has been fully fixed in server/v2.2.1 together with hydraidectl/v0.2.1.

All users are strongly advised to upgrade:

1. Update to hydraidectl v0.2.1
2. Re-initialize server instances with hydraidectl init into a new folder. This generates the required certificate files, downloads the latest binaries, and sets up the necessary environment variables.

For migration help, join the community Discord: https://discord.gg/xE2YSkzFRm or open a GitHub Discussion.
If anything does not work, please report it.

## Which versions are affected by GHSA-qp7j-x725-g67f?

5 open source packages ship an affected version, including github.com/hydraide/hydraide.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/hydraide/hydraide` | Go | All versions | 0.0.0-20250816184905-1256db38c33c |
| `github.com/hydraide/hydraide` | Go | All versions | 0.0.0-20250816184905-1256db38c33c |
| `github.com/hydraide/hydraide` | Go | All versions | 0.0.0-20250816184905-1256db38c33c |
| `github.com/hydraide/hydraide` | Go | From 2.1.1 | 2.2.1 |
| `github.com/hydraide/hydraide` | Go | From 2.1.1 | 2.2.1 |

## How do I fix GHSA-qp7j-x725-g67f?

Upgrade github.com/hydraide/hydraide to a fixed version for your release line: 0.0.0-20250816184905-1256db38c33c or 2.2.1.

## Is GHSA-qp7j-x725-g67f being exploited?

There is no known exploitation of GHSA-qp7j-x725-g67f in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-qp7j-x725-g67f and fix it if it is affected.

What it is: GHSA-qp7j-x725-g67f is an authentication bypass vulnerability in github.com/hydraide/hydraide, published on 19 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-qp7j-x725-g67f in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/hydraide/hydraide (Go): affected all versions; fixed in 0.0.0-20250816184905-1256db38c33c
- github.com/hydraide/hydraide (Go): affected all versions; fixed in 0.0.0-20250816184905-1256db38c33c
- github.com/hydraide/hydraide (Go): affected all versions; fixed in 0.0.0-20250816184905-1256db38c33c
- github.com/hydraide/hydraide (Go): affected from 2.1.1; fixed in 2.2.1
- github.com/hydraide/hydraide (Go): affected from 2.1.1; fixed in 2.2.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-qp7j-x725-g67f/ (Markdown: https://insights.sbomify.com/GHSA-qp7j-x725-g67f/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-qp7j-x725-g67f

---
From sbomify Insights: https://insights.sbomify.com/GHSA-qp7j-x725-g67f/
Summaries are generated and may contain mistakes; the official description above is the record.