Vulnerability in Codenotary Immudb
CVE-2022-39199
immudb is a database with built-in cryptographic proof and verification. immudb client SDKs use server's UUID to distinguish between different server instance so that the client can connect to different immudb instances and keep the state for multiple servers. SDK does not validate this uuid and can accept any value reported by the server. A malicious server can change the reported UUID tricking the client to treat it as a different server thus accepting a state completely irrelevant to the one previously retrieved from the server. This issue has been patched in version 1.4.1. As a workaround, when initializing an immudb client object a custom state handler can be used to store the state. Providing custom implementation that ignores the server UUID can be used to ensure that even if the server changes the UUID, client will still consider it to be the same server.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 5.8 (Medium). Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:N/I:H/A:N.
EPSS exploit prediction
EPSS: 0.003 (18.8th percentile), scored .
Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 19th percentile — 18.8% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.003 · newest: 0.003 · change: +0.000
Affected products
- Codenotary Immudb — versions < 1.4.1
Weakness classification (CWE)
References
- github.com/codenotary/immudb/security/advisories/GHSA-6cqj-6969-p57x (Third Party Advisory)
- github.com/codenotary/immudb/releases/tag/v1.4.1 (Third Party Advisory, Release Notes)
Frequently asked questions
- What is CVE-2022-39199?
- CVE-2022-39199 is a medium-severity vulnerability in Codenotary Immudb, classified under Insufficient Verification of Data Authenticity. CVSS score: 5.8/10. Published 2022-11-22.
- How severe is CVE-2022-39199?
- Medium severity. CVSS v3 base score is 5.8 out of 10.