GHSA-4WHX-7P29-MQ22

Vulnerability from github – Published: 2022-06-06 21:22 – Updated: 2025-07-09 15:49
VLAI?
Summary
TiDB authentication bypass vulnerability
Details

Impact

Under certain conditions, an attacker can construct malicious authentication requests to bypass the authentication process, resulting in privilege escalation or unauthorized access. Only users using TiDB 5.3.0 are affected by this vulnerability.

Patches

Please upgrade to TiDB 5.3.1 or higher version

Workarounds

You can also mitigate risks by taking the following measures. Option 1: Turn off SEM (Security Enhanced Mode). Option 2: Disable local login for non-root accounts and ensure that the same IP cannot be logged in as root or normal user at the same time.

References

https://en.pingcap.com/download/

For more information

If you have any questions or comments about this advisory: * Email us at security@tidb.io

Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/pingcap/tidb"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "5.3.0"
            },
            {
              "fixed": "5.3.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.3.0"
      ]
    },
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/pingcap/tidb"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0.0.0-20210808221113-a7fdc2a05663"
            },
            {
              "fixed": "0.0.0-20220221072141-27ffd1126da1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/pingcap/tidb"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "1.1.0-beta.0.20210808221113-a7fdc2a05663"
            },
            {
              "fixed": "1.1.0-beta.0.20220221072141-27ffd1126da1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2022-31011"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-287"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2022-06-06T21:22:28Z",
    "nvd_published_at": "2022-05-31T20:15:00Z",
    "severity": "HIGH"
  },
  "details": "### Impact\nUnder certain conditions, an attacker can construct malicious authentication requests to bypass the authentication process, resulting in privilege escalation or unauthorized access.\nOnly users using TiDB 5.3.0 are affected by this vulnerability.\n\n### Patches\nPlease upgrade to TiDB 5.3.1 or higher version\n\n### Workarounds\nYou can also mitigate risks by taking the following measures.\nOption 1: Turn off SEM (Security Enhanced Mode).\nOption 2: Disable local login for non-root accounts and ensure that the same IP cannot be logged in as root or normal user at the same time.\n\n### References\nhttps://en.pingcap.com/download/\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at security@tidb.io",
  "id": "GHSA-4whx-7p29-mq22",
  "modified": "2025-07-09T15:49:23Z",
  "published": "2022-06-06T21:22:28Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/pingcap/tidb/security/advisories/GHSA-4whx-7p29-mq22"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2022-31011"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/pingcap/tidb"
    },
    {
      "type": "WEB",
      "url": "https://github.com/pingcap/tidb/releases/tag/v5.3.1"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ],
  "summary": "TiDB authentication bypass vulnerability"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

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…