x/vulndb: potential Go vuln in github.com/codenotary/immudb: CVE-2022-39199

[GoVulnBot]

CVE-2022-39199 references github.com/codenotary/immudb, which may be a Go module.

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.

References:

• NIST: https://nvd.nist.gov/vuln/detail/CVE-2022-39199
• JSON: https://github.com/CVEProject/cvelist/tree/f37776bba22890c2e19d205eeafe73c7e8c7f0c2/2022/39xxx/CVE-2022-39199.json
• web: https://github.com/codenotary/immudb/security/advisories/GHSA-6cqj-6969-p57x
• web: https://github.com/codenotary/immudb/releases/tag/v1.4.1
• Imported by: https://pkg.go.dev/github.com/codenotary/immudb?tab=importedby

See doc/triage.md for instructions on how to triage this report.

modules:
  - module: github.com/codenotary/immudb
    packages:
      - package: immudb
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.

cves:
  - CVE-2022-39199
references:
  - web: https://github.com/codenotary/immudb/security/advisories/GHSA-6cqj-6969-p57x
  - web: https://github.com/codenotary/immudb/releases/tag/v1.4.1

[jba]

Duplicate of #1118

[julieqiu]

Closing as duplicate of #1118.