Skip to content

TiDB authentication bypass vulnerability

High severity GitHub Reviewed Published May 26, 2022 in pingcap/tidb • Updated Jul 9, 2025

Package

gomod github.com/pingcap/tidb (Go)

Affected versions

= 5.3.0
>= 0.0.0-20210808221113-a7fdc2a05663, < 0.0.0-20220221072141-27ffd1126da1
>= 1.1.0-beta.0.20210808221113-a7fdc2a05663, < 1.1.0-beta.0.20220221072141-27ffd1126da1

Patched versions

5.3.1
0.0.0-20220221072141-27ffd1126da1
1.1.0-beta.0.20220221072141-27ffd1126da1

Description

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:

References

@haohaoxuex2005 haohaoxuex2005 published to pingcap/tidb May 26, 2022
Published by the National Vulnerability Database May 31, 2022
Published to the GitHub Advisory Database Jun 6, 2022
Reviewed Jun 6, 2022
Last updated Jul 9, 2025

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(23rd percentile)

Weaknesses

Improper Authentication

When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. Learn more on MITRE.

CVE ID

CVE-2022-31011

GHSA ID

GHSA-4whx-7p29-mq22

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.