CVE-2022-36111 immundb has insufficient verification of data authenticity
A malicious server can trick the immudb client SDK into accepting falsified proofs, allowing transaction replacement and bypassing cryptographic verification.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2022-36111?
CVE-2022-36111 is a medium-severity vulnerability in codenotary immudb, published on 23 Nov 2022. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Official description
immudb is a database with built-in cryptographic proof and verification. In versions prior to 1.4.1, a malicious immudb server can provide a falsified proof that will be accepted by the client SDK signing a falsified transaction replacing the genuine one. This situation can not be triggered by a genuine immudb server and requires the client to perform a specific list of verified operations resulting in acceptance of an invalid state value. This vulnerability only affects immudb client SDKs, the immudb server itself is not affected by this vulnerability. This issue has been patched in version 1.4.1.
Weakness: CWE-345
Which versions are affected by CVE-2022-36111?
3 open source packages ship an affected version, including github.com/codenotary/immudb. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
github.com/codenotary/immudb Go | All versions | 1.4.1 |
github.com/codenotary/immudb Go | All versions | 1.4.1 |
github.com/codenotary/immudb Go | All versions | 1.4.1 |
Products include Codenotary Immudb.
How do I fix CVE-2022-36111?
Upgrade github.com/codenotary/immudb to 1.4.1 or later.
Is CVE-2022-36111 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-36111 exists.
Other vulnerabilities in codenotary immudb
Sources
Also known as GHSA-672p-m5jq-mrh8, GO-2022-1117.