# CVE-2024-0105: Privilege escalation in BlueField 1

> Attackers can exploit improper privilege handling in NVIDIA ConnectX firmware to cause denial of service, tamper with data, and disclose limited information.

- **Severity:** High 8.9 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:L/I:H/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:** 1 Nov 2024
- **Updated:** 1 Nov 2024
- **Also known as:** GHSA-cp5j-wrwq-37jx

## What is CVE-2024-0105?

CVE-2024-0105 is a high-severity vulnerability in NVIDIA BlueField 1, published on 1 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

NVIDIA ConnectX Firmware contains a vulnerability where an attacker may cause an improper handling of insufficient privileges issue. A successful exploit of this vulnerability may lead to denial of service, data tampering, and limited information disclosure.

Weakness: CWE-274 (Improper Handling of Insufficient Privileges)

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


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

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

## Is CVE-2024-0105 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-0105 is a high-severity vulnerability in NVIDIA BlueField 1, published on 1 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-0105 in the wild and no public exploit code.

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

## Sources

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

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