CVE-2022-39199

Source
https://nvd.nist.gov/vuln/detail/CVE-2022-39199
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-39199.json
Aliases
Published
2022-11-22T20:15:11Z
Modified
2023-11-29T09:49:20.339363Z
Details

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.

References

Affected packages

Git / github.com/codenotary/immudb

Affected ranges

Type
GIT
Repo
https://github.com/codenotary/immudb
Events
Introduced
0The exact introduced commit is unknown
Fixed

Affected versions

cnlc-2.*

cnlc-2.2

v0.*

v0.0.0-20200206
v0.6.0
v0.6.0-RC1
v0.6.0-RC2
v0.6.1
v0.6.2
v0.7.0
v0.8.0
v0.8.1
v0.9.0
v0.9.0-RC1
v0.9.0-RC2
v0.9.1
v0.9.2

v1.*

v1.0.0
v1.0.1
v1.0.5
v1.1.0
v1.2.0
v1.2.0-RC1
v1.2.1
v1.2.2
v1.2.3
v1.2.3-RC1
v1.2.4
v1.2.4-RC1
v1.3.0
v1.3.0-RC1
v1.3.1
v1.3.1-RC1
v1.3.2
v1.3.2-RC1
v1.4.0
v1.4.0-RC1
v1.4.0-RC2
v1.4.1-RC1