Filtered by vendor Pingcap Subscriptions
Filtered by product Tidb Subscriptions
Total 5 CVE
CVE Vendors Products Updated CVSS v3.1
CVE-2022-3023 1 Pingcap 1 Tidb 2024-11-21 9.8 Critical
Use of Externally-Controlled Format String in GitHub repository pingcap/tidb prior to 6.4.0, 6.1.3.
CVE-2022-34969 1 Pingcap 1 Tidb 2024-11-21 7.5 High
PingCAP TiDB v6.1.0 was discovered to contain a NULL pointer dereference.
CVE-2022-31011 1 Pingcap 1 Tidb 2024-11-21 7.8 High
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.
CVE-2024-41433 1 Pingcap 1 Tidb 2024-10-01 9.8 Critical
PingCAP TiDB v8.1.0 was discovered to contain a buffer overflow via the component expression.ExplainExpressionList. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted input. NOTE: PingCAP maintains that the actual reproduction of this issue did not cause the security impact of service interruption to other users. They argue that this is a complex query bug and not a DoS vulnerability.
CVE-2024-41434 1 Pingcap 1 Tidb 2024-09-25 4.3 Medium
PingCAP TiDB v8.1.0 was discovered to contain a buffer overflow via the component (*Column).GetDecimal. This allows attackers to cause a Denial of Service (DoS) via a crafted input to the 'RemoveUnnecessaryFirstRow', it will check the expression between 'Agg' and 'GroupBy', but does not check the return type. NOTE: PingCAP disputes this, arguing that reproduction did not cause the security impact of service interruption to other users. They maintain it is a complex query bug in the product but not a DoS.