CVE-2022-39199
"Immudb Server UUID Bypass Information Disclosure Vulnerability"
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.
INFO
Published Date :
Nov. 22, 2022, 8:15 p.m.
Last Modified :
Nov. 21, 2024, 7:17 a.m.
Source :
[email protected]
Remotely Exploitable :
Yes !
Impact Score :
3.6
Exploitability Score :
2.2
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2022-39199
.
URL | Resource |
---|---|
https://github.com/codenotary/immudb/releases/tag/v1.4.1 | Release Notes Third Party Advisory |
https://github.com/codenotary/immudb/security/advisories/GHSA-6cqj-6969-p57x | Third Party Advisory |
https://github.com/codenotary/immudb/releases/tag/v1.4.1 | Release Notes Third Party Advisory |
https://github.com/codenotary/immudb/security/advisories/GHSA-6cqj-6969-p57x | Third Party Advisory |
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2022-39199
vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2022-39199
vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by af854a3a-2127-422b-91ae-364da2661108
Nov. 21, 2024
Action Type Old Value New Value Added Reference https://github.com/codenotary/immudb/releases/tag/v1.4.1 Added Reference https://github.com/codenotary/immudb/security/advisories/GHSA-6cqj-6969-p57x -
CVE Modified by [email protected]
May. 14, 2024
Action Type Old Value New Value -
Initial Analysis by [email protected]
Nov. 26, 2022
Action Type Old Value New Value Added CVSS V3.1 NIST AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N Changed Reference Type https://github.com/codenotary/immudb/releases/tag/v1.4.1 No Types Assigned https://github.com/codenotary/immudb/releases/tag/v1.4.1 Release Notes, Third Party Advisory Changed Reference Type https://github.com/codenotary/immudb/security/advisories/GHSA-6cqj-6969-p57x No Types Assigned https://github.com/codenotary/immudb/security/advisories/GHSA-6cqj-6969-p57x Third Party Advisory Added CPE Configuration OR *cpe:2.3:a:codenotary:immudb:*:*:*:*:*:*:*:* versions up to (excluding) 1.4.1
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2022-39199
is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2022-39199
weaknesses.
Exploit Prediction
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days.
0.06 }} 0.00%
score
0.26714
percentile