Lack of proper validation of server UUID can be used by the server to trick the client to accept invalid proofs
Moderate severity
GitHub Reviewed
Published
Nov 21, 2022
in
codenotary/immudb
•
Updated Feb 14, 2023
Description
Published to the GitHub Advisory Database
Nov 21, 2022
Reviewed
Nov 21, 2022
Published by the National Vulnerability Database
Nov 22, 2022
Last updated
Feb 14, 2023
Impact
immudb 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.
Patches
The following Go SDK versions are not vulnerable:
Workarounds
When 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 information
If you have any questions or comments about this advisory:
References