dbcve.org
TidbApplication · Pingcap

CVE-2022-31011

HIGH · 7.8 CVSS v3.1 Published 2022-05-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
TiDB is an open-source NewSQL database that supports Hybrid Transactional and Analytical Processing (HTAP) workloads. 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. TiDB version 5.3.1 contains a patch for this issue. Other mitigation strategies include turning off Security Enhanced Mode (SEM), disabling local login for non-root accounts, and ensuring that the same IP cannot be logged in as root and normal user at the same time.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

TiDB 5.3.0 contains an authentication bypass vulnerability where attackers can construct malicious authentication requests to bypass the authentication process under certain conditions, potentially achieving privilege escalation or unauthorized access.

MitigationDisable Security Enhanced Mode (SEM), disable local login for non-root accounts, and ensure the same IP cannot be logged in as both root and normal user simultaneously. Upgrading to TiDB 5.3.1 is recommended.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
TidbApplication
Affected:= 5.3.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check TiDB server version
    Run `tidb-server -V` or execute `select @@version;` in the TiDB mysql client to retrieve the exact installed version number
    Affected if Version is exactly 5.3.0 (other versions are not affected)
  2. Check Security Enhanced Mode (SEM) status
    Inspect TiDB configuration file (tidb.toml) or run `show config where name like '%security.enablesem%';` in TiDB to check if SEM is enabled
    Affected if SEM is disabled - the vulnerability applies when SEM is not active
  3. Verify local login configuration for non-root accounts
    Query user account settings using `select user, host, plugin from mysql.user where user != 'root';` to check if non-root accounts are permitted to log in locally
    Affected if Local login is enabled for non-root users
  4. Check for shared IP login between root and normal users
    Review user host specifications in the mysql.user table to determine if the same IP address can authenticate as both root and a regular user account
    Affected if The same IP can log in as both root and a non-root user simultaneously

Environment is affected if running TiDB version 5.3.0 with SEM disabled while allowing local login for non-root accounts where root and normal users can log in from the same IP address.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable Security Enhanced Mode (SEM), disable local login for non-root accounts, and ensure the same IP cannot be logged in as both root and normal user simultaneously. Upgrading to TiDB 5.3.1 is recommended.

Recommended fix High confidence

TiDB 5.3.1

  1. Back up your existing TiDB 5.3.0 database including all data and configuration files
  2. Stop the TiDB 5.3.0 services (tidb-server, tikv-server, pd-server)
  3. Upgrade TiDB by installing version 5.3.1
  4. Verify the upgrade by checking that TiDB services start successfully and the version reports 5.3.1
  5. Test that authentication is working correctly and the vulnerability is mitigated

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Tidb Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,300
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,680.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-31011 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-31011 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data