# CVE-2022-39199: Lack of proper validation in immudb

> A malicious immudb server can spoof its UUID to trick clients into accepting invalid state proofs, bypassing cryptographic verification.

- **Severity:** Medium 5.8 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Nov 2022
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-6cqj-6969-p57x, GO-2022-1118

## What is CVE-2022-39199?

CVE-2022-39199 is a medium-severity vulnerability in codenotary immudb, published on 22 Nov 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

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.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

## Which versions are affected by CVE-2022-39199?

3 open source packages ship an affected version, including github.com/codenotary/immudb. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/codenotary/immudb` | Go | All versions | 1.4.1 |
| `github.com/codenotary/immudb` | Go | All versions | 1.4.1 |
| `github.com/codenotary/immudb` | Go | All versions | 1.4.1 |

Products: Codenotary Immudb.

## How do I fix CVE-2022-39199?

Upgrade github.com/codenotary/immudb to 1.4.1 or later.

## Is CVE-2022-39199 being exploited?

There is no known exploitation of CVE-2022-39199 in the wild and no public exploit code.

## Other vulnerabilities in codenotary immudb

- [CVE-2024-41262](https://insights.sbomify.com/CVE-2024-41262/): Information disclosure in n/a (high 7.4)
- [CVE-2022-36111](https://insights.sbomify.com/CVE-2022-36111/): immundb has insufficient verification of data authenticity (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-39199 and fix it if it is affected.

What it is: CVE-2022-39199 is a medium-severity vulnerability in codenotary immudb, published on 22 Nov 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-39199 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/codenotary/immudb (Go): affected all versions; fixed in 1.4.1
- github.com/codenotary/immudb (Go): affected all versions; fixed in 1.4.1
- github.com/codenotary/immudb (Go): affected all versions; fixed in 1.4.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-39199/ (Markdown: https://insights.sbomify.com/CVE-2022-39199/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-39199
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-39199
- OSV: https://osv.dev/vulnerability/CVE-2022-39199

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-39199/
Summaries are generated and may contain mistakes; the official description above is the record.