# TiDB authentication bypass vulnerability

Advisory record · `GHSA-4whx-7p29-mq22`

- **Identifiers:** `GHSA-4whx-7p29-mq22` · `CVE-2022-31011`
- **State:** Confirmed
- **Severity:** CVSS 7.8 High
- **Critical:** No
- **Weakness (CWE):** [CWE-287](https://cwe.mitre.org/data/definitions/287.html)
- **Tags:** [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md)
- **Published:** 6 Jun 2022
- **Updated:** 9 Jul 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 6 Jun 2022, 21:22 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/pingcap/tidb` (Go): affected `>=5.3.0, <5.3.1 || >=0.0.0-20210808221113-a7fdc2a05663, <0.0.0-20220221072141-27ffd1126da1 || >=1.1.0-beta.0.20210808221113-a7fdc2a05663, <1.1.0-beta.0.20220221072141-27ffd1126da1`; fixed in `5.3.1`, `0.0.0-20220221072141-27ffd1126da1`, `1.1.0-beta.0.20220221072141-27ffd1126da1`

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.8 High, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0032, the 25th percentile, on 21 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the GitHub Advisory Database, published 6 Jun 2022. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-4whx-7p29-mq22](https://github.com/advisories/GHSA-4whx-7p29-mq22)
- [OSV: GHSA-4whx-7p29-mq22](https://osv.dev/vulnerability/GHSA-4whx-7p29-mq22)
- <https://github.com/pingcap/tidb/security/advisories/GHSA-4whx-7p29-mq22>
- <https://nvd.nist.gov/vuln/detail/CVE-2022-31011>
- <https://github.com/pingcap/tidb>
- <https://github.com/pingcap/tidb/releases/tag/v5.3.1>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-4whx-7p29-mq22>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-4whx-7p29-mq22/>. Everything for agents: <https://agentprime.io/llms.txt>.
