CVE-2022-36111: Insufficient Verification of Data Authenticity
(updated )
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
- github.com/advisories/GHSA-672p-m5jq-mrh8
- 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
Code Behaviors & Features
Detect and mitigate CVE-2022-36111 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →