CVE-2022-31011

TiDB authentication bypass vulnerability

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 [email protected]

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.

The application does not adequately verify the identity of a user, device, or process before granting access. Typical impact: unauthorized access to functions or data reserved for authenticated parties.

CVE-2022-31011 has a CVSS score of 7.8 (High). The vector is requires local access, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (5.3.1, 0.0.0-20220221072141-27ffd1126da1, 1.1.0-beta.0.20220221072141-27ffd1126da1); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

Please upgrade to TiDB 5.3.1 or higher version

1. What is CVE-2022-31011? CVE-2022-31011 is a high-severity improper authentication vulnerability in github.com/pingcap/tidb (go), affecting versions = 5.3.0. It is fixed in 5.3.1, 0.0.0-20220221072141-27ffd1126da1, 1.1.0-beta.0.20220221072141-27ffd1126da1. The application does not adequately verify the identity of a user, device, or process before granting access.
2. How severe is CVE-2022-31011? CVE-2022-31011 has a CVSS score of 7.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/pingcap/tidb are affected by CVE-2022-31011? github.com/pingcap/tidb (go) versions = 5.3.0 is affected.
4. Is there a fix for CVE-2022-31011? Yes. CVE-2022-31011 is fixed in 5.3.1, 0.0.0-20220221072141-27ffd1126da1, 1.1.0-beta.0.20220221072141-27ffd1126da1. Upgrade to this version or later.
5. Is CVE-2022-31011 exploitable, and should I be worried? Whether CVE-2022-31011 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2022-31011 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2022-31011?
   • Upgrade github.com/pingcap/tidb to 5.3.1 or later
   • Upgrade github.com/pingcap/tidb to 0.0.0-20220221072141-27ffd1126da1 or later
   • Upgrade github.com/pingcap/tidb to 1.1.0-beta.0.20220221072141-27ffd1126da1 or later

Other vulnerabilities in github.com/pingcap/tidb