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

> Attackers can cause a Denial of Service in KIA Seltos instrument clusters via ECU reset UDS service, though the vulnerability is disputed by the supplier.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Nov 2024
- **Updated:** 10 Jan 2025
- **Also known as:** GHSA-55j6-hcxw-2cg2

## What is CVE-2024-51072?

CVE-2024-51072 is a medium-severity denial of service vulnerability in n/a, published on 22 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue in KIA Seltos vehicle instrument cluster with software and hardware v1.0 allows attackers to cause a Denial of Service (DoS) via ECU reset UDS service. NOTE: this is disputed by the Supplier because the findings came from a potentially unrealistic test environment (an isolated ECU part that was not in a vehicle), and because the ECUReset specification does not allow a manufacturer to require SecurityAccess and Authentication.

Weakness: CWE-346 (Origin Validation Error)

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


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

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

## Is CVE-2024-51072 being exploited?

There is no known exploitation of CVE-2024-51072 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2024-51072 is a medium-severity denial of service vulnerability in n/a, published on 22 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-51072 in the wild and no public exploit code.

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-51072/ (Markdown: https://insights.sbomify.com/CVE-2024-51072/index.md)
```

## Sources

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

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