CVE-2022-39199

Lack of proper validation of server UUID can be used by the server to trick the client to accept invalid proofs

Workarounds

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.

For more information

If you have any questions or comments about this advisory:

• Open a discussion in immudb Discussions
• Email us at [email protected]

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.

CVE-2022-39199 has a CVSS score of 5.8 (Medium). The vector is network-reachable, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.4.1); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

The following Go SDK versions are not vulnerable:

1. What is CVE-2022-39199? CVE-2022-39199 is a medium-severity security vulnerability in github.com/codenotary/immudb (go), affecting versions < 1.4.1. It is fixed in 1.4.1.
2. How severe is CVE-2022-39199? CVE-2022-39199 has a CVSS score of 5.8 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/codenotary/immudb are affected by CVE-2022-39199? github.com/codenotary/immudb (go) versions < 1.4.1 is affected.
4. Is there a fix for CVE-2022-39199? Yes. CVE-2022-39199 is fixed in 1.4.1. Upgrade to this version or later.
5. Is CVE-2022-39199 exploitable, and should I be worried? Whether CVE-2022-39199 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2022-39199 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2022-39199? Upgrade github.com/codenotary/immudb to 1.4.1 or later.

Other vulnerabilities in github.com/codenotary/immudb