CVE-2022-39199: Lack of proper validation in immudb

Severity: medium (CVSS 5.9 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.3% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2022-11-22 · updated 2026-06-17
Weakness: CWE-345

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 products

codenotary immudb: before 1.4.1 — fixed in 1.4.1

How to fix

Upgrade to a fixed version: codenotary immudb 1.4.1. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2022-39199 or the next vulnerability affects your stack