GSD-2022-39199

Vulnerability from gsd - Updated: 2023-12-13 01:19
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.
Aliases
Aliases

{
  "GSD": {
    "alias": "CVE-2022-39199",
    "description": "immudb is a database with built-in cryptographic proof and verification. immudb client SDKs use server\u0027s 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.",
    "id": "GSD-2022-39199"
  },
  "gsd": {
    "metadata": {
      "exploitCode": "unknown",
      "remediation": "unknown",
      "reportConfidence": "confirmed",
      "type": "vulnerability"
    },
    "osvSchema": {
      "aliases": [
        "CVE-2022-39199"
      ],
      "details": "immudb is a database with built-in cryptographic proof and verification. immudb client SDKs use server\u0027s 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.",
      "id": "GSD-2022-39199",
      "modified": "2023-12-13T01:19:20.686426Z",
      "schema_version": "1.4.0"
    }
  },
  "namespaces": {
    "cve.org": {
      "CVE_data_meta": {
        "ASSIGNER": "security-advisories@github.com",
        "ID": "CVE-2022-39199",
        "STATE": "PUBLIC",
        "TITLE": "Lack of proper validation in immudb "
      },
      "affects": {
        "vendor": {
          "vendor_data": [
            {
              "product": {
                "product_data": [
                  {
                    "product_name": "immudb",
                    "version": {
                      "version_data": [
                        {
                          "version_value": "\u003c 1.4.1"
                        }
                      ]
                    }
                  }
                ]
              },
              "vendor_name": "codenotary"
            }
          ]
        }
      },
      "data_format": "MITRE",
      "data_type": "CVE",
      "data_version": "4.0",
      "description": {
        "description_data": [
          {
            "lang": "eng",
            "value": "immudb is a database with built-in cryptographic proof and verification. immudb client SDKs use server\u0027s 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."
          }
        ]
      },
      "impact": {
        "cvss": {
          "attackComplexity": "HIGH",
          "attackVector": "NETWORK",
          "availabilityImpact": "NONE",
          "baseScore": 5.8,
          "baseSeverity": "MEDIUM",
          "confidentialityImpact": "NONE",
          "integrityImpact": "HIGH",
          "privilegesRequired": "HIGH",
          "scope": "CHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:N/I:H/A:N",
          "version": "3.1"
        }
      },
      "problemtype": {
        "problemtype_data": [
          {
            "description": [
              {
                "lang": "eng",
                "value": "CWE-345: Insufficient Verification of Data Authenticity"
              }
            ]
          }
        ]
      },
      "references": {
        "reference_data": [
          {
            "name": "https://github.com/codenotary/immudb/security/advisories/GHSA-6cqj-6969-p57x",
            "refsource": "CONFIRM",
            "url": "https://github.com/codenotary/immudb/security/advisories/GHSA-6cqj-6969-p57x"
          },
          {
            "name": "https://github.com/codenotary/immudb/releases/tag/v1.4.1",
            "refsource": "MISC",
            "url": "https://github.com/codenotary/immudb/releases/tag/v1.4.1"
          }
        ]
      },
      "source": {
        "advisory": "GHSA-6cqj-6969-p57x",
        "discovery": "UNKNOWN"
      }
    },
    "gitlab.com": {
      "advisories": [
        {
          "affected_range": "\u003cv1.4.1",
          "affected_versions": "All versions before 1.4.1",
          "cvss_v3": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N",
          "cwe_ids": [
            "CWE-1035",
            "CWE-345",
            "CWE-937"
          ],
          "date": "2023-02-14",
          "description": "immudb is a database with built-in cryptographic proof and verification. immudb client SDKs use server\u0027s 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.",
          "fixed_versions": [
            "v1.4.1"
          ],
          "identifier": "CVE-2022-39199",
          "identifiers": [
            "GHSA-6cqj-6969-p57x",
            "CVE-2022-39199"
          ],
          "not_impacted": "All versions starting from 1.4.1",
          "package_slug": "go/github.com/codenotary/immudb",
          "pubdate": "2022-11-21",
          "solution": "Upgrade to version 1.4.1 or above.",
          "title": "Insufficient Verification of Data Authenticity",
          "urls": [
            "https://github.com/codenotary/immudb/security/advisories/GHSA-6cqj-6969-p57x",
            "https://nvd.nist.gov/vuln/detail/CVE-2022-39199",
            "https://github.com/codenotary/immudb/releases/tag/v1.4.1",
            "https://github.com/codenotary/immudb/commit/cade04756ff3f0a3b9e8d24149062744574adf5d",
            "https://pkg.go.dev/vuln/GO-2022-1118",
            "https://github.com/advisories/GHSA-6cqj-6969-p57x"
          ],
          "uuid": "3852a736-b6c4-46d4-bf6d-eb0e8886db78",
          "versions": [
            {
              "commit": {
                "sha": "ad7623ce74bb3257d78af75941d494883591141a",
                "tags": [
                  "v1.4.1"
                ],
                "timestamp": "20221121134825"
              },
              "number": "v1.4.1"
            }
          ]
        },
        {
          "affected_range": "\u003cv1.4.1",
          "affected_versions": "All versions before 1.4.1",
          "cvss_v3": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N",
          "cwe_ids": [
            "CWE-1035",
            "CWE-345",
            "CWE-937"
          ],
          "date": "2022-11-26",
          "description": "immudb is a database with built-in cryptographic proof and verification. immudb client SDKs use server\u0027s 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.",
          "fixed_versions": [
            "v1.4.1"
          ],
          "identifier": "CVE-2022-39199",
          "identifiers": [
            "CVE-2022-39199",
            "GHSA-6cqj-6969-p57x",
            "GMS-2022-6878"
          ],
          "not_impacted": "",
          "package_slug": "go/github.com/codenotary/immudb/pkg/client",
          "pubdate": "2022-11-22",
          "solution": "Upgrade to version 1.4.1 or above.",
          "title": "Insufficient Verification of Data Authenticity",
          "urls": [
            "https://nvd.nist.gov/vuln/detail/CVE-2022-39199",
            "https://github.com/codenotary/immudb/releases/tag/v1.4.1",
            "https://github.com/codenotary/immudb/security/advisories/GHSA-6cqj-6969-p57x",
            "https://github.com/advisories/GHSA-6cqj-6969-p57x"
          ],
          "uuid": "1b3ee15d-9afe-4c88-aa3f-fb813ec4ee13",
          "versions": [
            {
              "commit": {
                "sha": "ad7623ce74bb3257d78af75941d494883591141a",
                "tags": [
                  "v1.4.1"
                ],
                "timestamp": "20221121134825"
              },
              "number": "v1.4.1"
            }
          ]
        },
        {
          "affected_range": "\u003c0",
          "affected_versions": "All versions before 1.4.1",
          "cwe_ids": [
            "CWE-1035",
            "CWE-937"
          ],
          "date": "2022-11-21",
          "description": "### Impact\n\nimmudb client SDKs use server\u0027s 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.\n\n### Patches\n\nThe following Go SDK versions are not vulnerable\n\n| **SDK** | **Version** |\n|-------|------------|\n| [go](pkg.go.dev/github.com/codenotary/immudb/pkg/client) | 1.4.1 |\n\n### Workarounds\n\nWhen 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.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Open a discussion in [immudb Discussions](https://github.com/codenotary/immudb/discussions/new)\n* Email us at [immudb-security@codenotary.com](mailto:immudb-security@codenotary.com)\n",
          "fixed_versions": [
            "v1.4.1"
          ],
          "identifier": "GMS-2022-6878",
          "identifiers": [
            "GHSA-6cqj-6969-p57x",
            "GMS-2022-6878",
            "CVE-2022-39199"
          ],
          "not_impacted": "All versions starting from 1.4.1",
          "package_slug": "go/github.com/codenotary/immudb/pkg/client",
          "pubdate": "2022-11-21",
          "solution": "Upgrade to version 1.4.1 or above.",
          "title": "Duplicate of ./go/github.com/codenotary/immudb/pkg/client/CVE-2022-39199.yml",
          "urls": [
            "https://github.com/codenotary/immudb/security/advisories/GHSA-6cqj-6969-p57x",
            "https://github.com/advisories/GHSA-6cqj-6969-p57x"
          ],
          "uuid": "9541905d-c6d4-4321-b930-2c56f2e504cf",
          "versions": [
            {
              "commit": {
                "sha": "ad7623ce74bb3257d78af75941d494883591141a",
                "tags": [
                  "v1.4.1"
                ],
                "timestamp": "20221121134825"
              },
              "number": "v1.4.1"
            }
          ]
        }
      ]
    },
    "nvd.nist.gov": {
      "configurations": {
        "CVE_data_version": "4.0",
        "nodes": [
          {
            "children": [],
            "cpe_match": [
              {
                "cpe23Uri": "cpe:2.3:a:codenotary:immudb:*:*:*:*:*:*:*:*",
                "cpe_name": [],
                "versionEndExcluding": "1.4.1",
                "vulnerable": true
              }
            ],
            "operator": "OR"
          }
        ]
      },
      "cve": {
        "CVE_data_meta": {
          "ASSIGNER": "security-advisories@github.com",
          "ID": "CVE-2022-39199"
        },
        "data_format": "MITRE",
        "data_type": "CVE",
        "data_version": "4.0",
        "description": {
          "description_data": [
            {
              "lang": "en",
              "value": "immudb is a database with built-in cryptographic proof and verification. immudb client SDKs use server\u0027s 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."
            }
          ]
        },
        "problemtype": {
          "problemtype_data": [
            {
              "description": [
                {
                  "lang": "en",
                  "value": "CWE-345"
                }
              ]
            }
          ]
        },
        "references": {
          "reference_data": [
            {
              "name": "https://github.com/codenotary/immudb/releases/tag/v1.4.1",
              "refsource": "MISC",
              "tags": [
                "Release Notes",
                "Third Party Advisory"
              ],
              "url": "https://github.com/codenotary/immudb/releases/tag/v1.4.1"
            },
            {
              "name": "https://github.com/codenotary/immudb/security/advisories/GHSA-6cqj-6969-p57x",
              "refsource": "CONFIRM",
              "tags": [
                "Third Party Advisory"
              ],
              "url": "https://github.com/codenotary/immudb/security/advisories/GHSA-6cqj-6969-p57x"
            }
          ]
        }
      },
      "impact": {
        "baseMetricV3": {
          "cvssV3": {
            "attackComplexity": "HIGH",
            "attackVector": "NETWORK",
            "availabilityImpact": "NONE",
            "baseScore": 5.9,
            "baseSeverity": "MEDIUM",
            "confidentialityImpact": "NONE",
            "integrityImpact": "HIGH",
            "privilegesRequired": "NONE",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N",
            "version": "3.1"
          },
          "exploitabilityScore": 2.2,
          "impactScore": 3.6
        }
      },
      "lastModifiedDate": "2022-11-26T03:32Z",
      "publishedDate": "2022-11-22T20:15Z"
    }
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…