# CVE-2024-34332: Privilege escalation in n/a

> An attacker can escalate privileges by sending a crafted buffer to the SiSoftware SANDRA kernel driver via DeviceIoControl.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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:** 10 Jun 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-h7v5-c8v4-f6pp

## What is CVE-2024-34332?

CVE-2024-34332 is a high-severity vulnerability in n/a, published on 10 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue in SiSoftware SANDRA v31.66 (SANDRA.sys 15.18.1.1) and before allows an attacker to escalate privileges via a crafted buffer sent to the Kernel Driver using the DeviceIoControl Windows API.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2024-34332 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-34332 is a high-severity vulnerability in n/a, published on 10 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-34332 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-34332/ (Markdown: https://insights.sbomify.com/CVE-2024-34332/index.md)
```

## Sources

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

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