5.4 Medium
CVSS3
Attack Vector
NETWORK
Attack Complexity
HIGH
Privileges Required
HIGH
User Interaction
REQUIRED
Scope
CHANGED
Confidentiality Impact
NONE
Integrity Impact
HIGH
Availability Impact
NONE
CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:N/I:H/A:N
0.001 Low
EPSS
Percentile
48.9%
In certain scenario 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.
immudb uses Merkle Tree enhanced with additional linear part to perform consistency proofs between two transactions. The linear part is built from the last leaf node of the Merkle Tree compensating for transactions that were not yet consumed by the Merkle Tree calculation.
The Merkle Tree part is then used to perform proofs for things that are in transaction range covered by the Merkle Tree where the linear part is used to check those that are not yet in the Merkle Tree.
When doing consistency checks between two immudb states, the linear proof part is not fully checked. In fact only the first (last Merkle Tree leaf) and the last (current DB state value) are checked against new Merkle Tree without ensuring that elements in the middle of that chain are correctly added as Merkle Tree leafs.
This lack of check means that the database can present different set of hashes on the linear proof part to what would later be used once those become part of the Merkle Tree. This property can be exploited by the database to expose two different transaction entries depending on the other transaction that the user requested consistency proof for.
In practice this could lead to a following scenario:
The following Go SDK versions is not vulnerable:
SDK | Version |
---|---|
go | 1.4.1 |
Invalid proofs can not be generated in a normal immudb server and will be detected by a genuine replica server.
To ensure that the server does not produce invalid proofs and to check that the history presented by the server
does not contain falsified transactions, one should run a genuine immudb replica server in a safe environment
and fully synchronize all databases with the primary.
If you have any questions or comments about this advisory:
CPE | Name | Operator | Version |
---|---|---|---|
github.com/codenotary/immudb | lt | 1.4.1 |
github.com/codenotary/immudb
github.com/codenotary/immudb/commit/7267d67e28be8f0257b71d734611a051593e8a81
github.com/codenotary/immudb/commit/acf7f1b3d62436ea5e038acea1fc6394f90ab1c6
github.com/codenotary/immudb/releases/tag/v1.4.1
github.com/codenotary/immudb/security/advisories/GHSA-672p-m5jq-mrh8
github.com/codenotary/immudb/tree/master/docs/security/vulnerabilities/linear-fake
nvd.nist.gov/vuln/detail/CVE-2022-36111
pkg.go.dev/github.com/codenotary/immudb/pkg/client
pkg.go.dev/vuln/GO-2022-1117