# CVE-2024-41434: Denial of service in n/a

> Attackers can cause a denial of service in TiDB via crafted input triggering a buffer overflow in decimal processing, though the vendor disputes the security impact.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Sep 2024
- **Updated:** 25 Sep 2024
- **Also known as:** GHSA-66rc-q43x-8675

## What is CVE-2024-41434?

CVE-2024-41434 is a medium-severity denial of service vulnerability in n/a, published on 3 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2024-41434?

It affects 1 product.


Products: Pingcap Tidb.

## How do I fix CVE-2024-41434?

No fix has been published for CVE-2024-41434 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-41434 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-41434 exists.

## Other vulnerabilities in n/a

- [CVE-2024-41433](https://insights.sbomify.com/CVE-2024-41433/): Memory corruption in n/a (critical 9.8)
- [CVE-2022-31011](https://insights.sbomify.com/CVE-2022-31011/): TiDB authentication bypass vulnerability (high 7.8)
- [CVE-2024-35618](https://insights.sbomify.com/CVE-2024-35618/): Null dereference in n/a (high 7.5)
- [CVE-2022-34969](https://insights.sbomify.com/CVE-2022-34969/): Null dereference in n/a (high 7.5)
- [CVE-2024-33809](https://insights.sbomify.com/CVE-2024-33809/): Memory corruption in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-41434 and fix it if it is affected.

What it is: CVE-2024-41434 is a medium-severity denial of service vulnerability in n/a, published on 3 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-41434 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-41434/ (Markdown: https://insights.sbomify.com/CVE-2024-41434/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-41434
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-41434
- OSV: https://osv.dev/vulnerability/CVE-2024-41434

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-41434/
Summaries are generated and may contain mistakes; the official description above is the record.