# CVE-2024-0115: Denial of service in NVIDIA CV-CUDA

> A user can cause denial of service and data loss in NVIDIA CV-CUDA via uncontrolled resource consumption in Python APIs.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Aug 2024
- **Updated:** 9 Aug 2024
- **Also known as:** GHSA-x73h-483r-8x6h

## What is CVE-2024-0115?

CVE-2024-0115 is a medium-severity denial of service vulnerability in NVIDIA CV-CUDA, published on 9 Aug 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

NVIDIA CV-CUDA for Ubuntu 20.04, Ubuntu 22.04, and Jetpack contains a vulnerability in Python APIs where a user may cause an uncontrolled resource consumption issue by a long running CV-CUDA Python process. A successful exploit of this vulnerability may lead to denial of service and data loss.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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

It affects 1 product.


Products: Nvidia Cv-Cuda.

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

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

## Is CVE-2024-0115 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-0115 is a medium-severity denial of service vulnerability in NVIDIA CV-CUDA, published on 9 Aug 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-0115 in the wild and no public exploit code.

Affected product: NVIDIA CV-CUDA. 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-0115/ (Markdown: https://insights.sbomify.com/CVE-2024-0115/index.md)
```

## Sources

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

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