CVE-2022-39199 Lack of proper validation in immudb

What is CVE-2022-39199?

CVE-2022-39199 is a medium-severity vulnerability in codenotary immudb, published on 22 Nov 2022. An attacker needs administrator access to exploit it, with no action from the victim.

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.

Weakness: CWE-345

Which versions are affected by CVE-2022-39199?

3 open source packages ship an affected version, including github.com/codenotary/immudb. It affects 1 product.

Products include Codenotary Immudb.

How do I fix CVE-2022-39199?

Upgrade github.com/codenotary/immudb to 1.4.1 or later.

Is CVE-2022-39199 being exploited?

There is no known exploitation of CVE-2022-39199 in the wild and no public exploit code.

Other vulnerabilities in codenotary immudb

• CVE-2024-41262 Information disclosure in n/a High 7.4
• CVE-2022-36111 immundb has insufficient verification of data authenticity Medium 5.4

Sources

• CVE record
• NVD
• OSV
• GitHub advisory
• How this page is made

Also known as GHSA-6cqj-6969-p57x, GO-2022-1118.