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.
See doc/triage.md for instructions on how to triage this report.
modules:
- module: github.com/codenotary/immudb
packages:
- package: immudb
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.
cves:
- CVE-2022-36111
references:
- web: https://github.com/codenotary/immudb/security/advisories/GHSA-672p-m5jq-mrh8
- web: https://github.com/codenotary/immudb/releases/tag/v1.4.1
- web: https://github.com/codenotary/immudb/tree/master/docs/security/vulnerabilities/linear-fake
- web: https://pkg.go.dev/github.com/codenotary/immudb/pkg/client
CVE-2022-36111 references github.com/codenotary/immudb, which may be a Go module.
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.
References:
See doc/triage.md for instructions on how to triage this report.