Vulnerability · Published Nov 22, 2022 · Assigned by GitHub_M
CVE-2022-39199Lack of proper validation in immudb
Medium 5.8
In plain English
A medium-severity insufficient verification of data authenticity in immudb from codenotary. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.3% (higher than 22% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official 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.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Go | github.com/codenotary/immudb | 1.4.1 | GHSA-6cqj-6969-p57x |
| Go | github.com/codenotary/immudb | 1.4.1 | GO-2022-1118 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| codenotary | immudb | < 1.4.1 |
Weakness: CWE-345 · Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:N/I:H/A:N