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
Link | Resource |
---|---|
https://github.com/codenotary/immudb/releases/tag/v1.4.1 | Release Notes Third Party Advisory |
https://github.com/codenotary/immudb/security/advisories/GHSA-672p-m5jq-mrh8 | Exploit Third Party Advisory |
https://github.com/codenotary/immudb/tree/master/docs/security/vulnerabilities/linear-fake | Exploit Third Party Advisory |
https://pkg.go.dev/github.com/codenotary/immudb/pkg/client | Third Party Advisory |
Configurations
History
No history.
Information
Published : 2022-11-23 18:15
Updated : 2024-02-28 19:51
NVD link : CVE-2022-36111
Mitre link : CVE-2022-36111
CVE.ORG link : CVE-2022-36111
JSON object : View
Products Affected
codenotary
- immudb
CWE
CWE-345
Insufficient Verification of Data Authenticity