Lack of proper validation of server UUID can be used by the server to trick the client to accept invalid proofs
Impactimmudb client SDKs use server's UUID to distinguish between different server instance so that the client can connect to different immudb instances and keep the state for multiple servers. SDK does not validate this uuid and can accept any value reported by the server. A malicious server can change the reported UUID tricking the client to treat it as a different server thus accepting a state completely irrelevant to the one previously retrieved from the server.PatchesThe following Go SDK versions are not vulnerable:| **SDK** | **Version** |
|-------|------------|
| [go](pkg.go.dev/github.com/codenotary/immudb/pkg/client) | 1.4.1 |WorkaroundsWhen initializing an immudb client object, a custom state handler can be used to store the state. Providing custom implementation that ignores the server UUID can be used to ensure that even if the server changes the UUID, client will still consider it to be the same server.For more informationIf you have any questions or comments about this advisory:Open a discussion in [immudb Discussions](https://github.com/codenotary/immudb/discussions/new)Email us at [immudb-security@codenotary.com](mailto:immudb-security@codenotary.com)