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

中 5.9CVE-2022-39199 · GHSA-6cqj-6969-p57x · GO-2022-1118 · 22/11/2022 公開 · 17/06/2026 更新

要点

CVE-2022-39199 は github.com/codenotary/immudb, immudb (codenotary) に影響する深刻度「中」 (CVSS 5.9) の脆弱性です。
今後30日間に悪用される確率（EPSS）：0.29%（全脆弱性の 22.1% より高い）。
対処：1.4.1 以降に更新してください。

パッケージ	影響を受けるバージョン	修正済みバージョン
github.com/codenotary/immudb Go	`< 1.4.1`	`1.4.1`
immudb codenotary	`< 1.4.1`	`1.4.1`

概要

Impact

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.

Patches

The following Go SDK versions are not vulnerable:

SDK	Version
go	1.4.1

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]

NVD の説明

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.