dbcve.org
ImmudbApplication · Codenotary

CVE-2022-39199

MEDIUM · 5.9 CVSS v3.1 Published 2022-11-22
Fix available
A fix is available. Upgrade to 1.4.1 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

immudb client SDKs use the server's UUID to distinguish between different server instances for maintaining client state. The SDK does not validate the UUID received from the server and accepts any value reported. A malicious or compromised server can exploit this by changing its reported UUID, causing the client to treat it as a different server and accept state that is completely irrelevant to previously retrieved data.

MitigationUpgrade immudb client SDKs to version 1.4.1 or later which contains the patch. Alternatively, implement a custom state handler that ignores the server UUID to ensure consistent state regardless of UUID changes.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ImmudbApplication
Affected:< 1.4.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the immudb client SDK in use
    Examine your project dependencies or vendor libraries to determine which immudb client SDK you are using (e.g., immudb4j for Java, immudb-py for Python, immudb-go for Go, immudb-node for Node.js, or immudb-c for .NET)
    Affected if You are using any immudb client SDK library in your application
  2. Determine the installed SDK version
    Run the appropriate command to inspect the installed version of your immudb client SDK: for Python use 'pip show immudb-py' or check your requirements.txt; for Java check your pom.xml or build.gradle; for Go check go.mod; for Node.js check package.json; for .NET check your .csproj or packages.config
    Affected if The displayed version number is below 1.4.1
  3. Verify UUID validation is not enforced
    Inspect the client initialization code to determine if the SDK has any built-in configuration to enforce or validate server UUID. Check the SDK documentation for any state handler options related to UUID validation or server identity verification
    Affected if No UUID validation or server identity verification is configured and the SDK version is below 1.4.1

You are affected if your immudb client SDK version is below 1.4.1 and your application relies on the default state handler without custom UUID validation logic.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.4.1 or later
Fixed in 1.4.1
Interim mitigation

Upgrade immudb client SDKs to version 1.4.1 or later which contains the patch. Alternatively, implement a custom state handler that ignores the server UUID to ensure consistent state regardless of UUID changes.

Recommended fix High confidence

1.4.1

  1. Identify the immudb version currently running using 'immudb version' or checking the deployment configuration
  2. Download immudb version 1.4.1 or later from the official GitHub releases (github.com/codenotary/immudb)
  3. Stop the currently running immudb service to prevent data corruption during upgrade
  4. Backup the immudb data directory to preserve existing data and state
  5. Install or replace the immudb binary with version 1.4.1
  6. Verify the installed version matches 1.4.1 using 'immudb version'
  7. Start the immudb service and verify normal operation
  8. If using immudb client SDKs, ensure client applications reconnect to verify the fix is effective
Caveat Review release notes for 1.4.1 to check for any breaking changes in API or configuration; minor version upgrades typically have minimal compatibility impact

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Immudb Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-39199 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-39199 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data