CVE-2022-31011 — tidb
HIGHCVE-2022-31011 is a high-severity (CVSS 7.8) Improper Authentication vulnerability in github.com/pingcap/tidb. A fix is available for github.com/pingcap/tidb — see the affected versions and patch details below.
TiDB authentication bypass vulnerability
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2022-31011.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2022-31011 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,567 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
github.com/pingcap/tidb🐹github.com/pingcap/tidb🐹github.com/pingcap/tidbReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
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:
- Email us at [email protected]
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/pingcap/tidb | ≥ 5.3.0&&< 5.3.1 | 5.3.1go get github.com/pingcap/tidb@v5.3.1 |
| 🐹Go | github.com/pingcap/tidb | ≥ 0.0.0-20210808221113-a7fdc2a05663&&< 0.0.0-20220221072141-27ffd1126da1 | 0.0.0-20220221072141-27ffd1126da1go get github.com/pingcap/tidb@v0.0.0-20220221072141-27ffd1126da1 |
| 🐹Go | github.com/pingcap/tidb | ≥ 1.1.0-beta.0.20210808221113-a7fdc2a05663&&< 1.1.0-beta.0.20220221072141-27ffd1126da1 | 1.1.0-beta.0.20220221072141-27ffd1126da1go get github.com/pingcap/tidb@v1.1.0-beta.0.20220221072141-27ffd1126da1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/pingcap/tidb, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/pingcap/tidb to 5.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-31011 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2022-31011 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2022-31011. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2022-31011 in your dependencies?
O3 Security finds CVE-2022-31011 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.