CVE-2022-39199
Description
immudb is a database with built-in cryptographic proof and verification. 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. This issue has been patched in version 1.4.1. As a workaround, 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.
How to fix
- codenotary immudb1.4.1 or later
- github.com/codenotary/immudb1.4.1 or later
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| codenotary immudb | v < 1.4.1 | 1.4.1 |
| github.com/codenotary/immudbGo | v < 1.4.1 | 1.4.1 |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.