# CVE-2021-34110: Privilege escalation in n/a

> A local unprivileged user can replace the application executable to execute arbitrary code with LocalSystem privileges due to incorrect file permissions.

- **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:** 8 Jul 2021
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-9jr3-q9q2-459g

## What is CVE-2021-34110?

CVE-2021-34110 is a high-severity vulnerability in n/a, published on 8 Jul 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

WinWaste.NET version 1.0.6183.16475 has incorrect permissions, allowing a local unprivileged user to replace the executable with a malicious file that will be executed with "LocalSystem" privileges.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2021-34110?

It affects 1 product.


Products: Nica Winwaste.net.

## How do I fix CVE-2021-34110?

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

## Is CVE-2021-34110 being exploited?

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

Public exploit code:

- WinWaste.NET 1.0.6183.16475 - Privilege Escalation due Incorrect Access Control (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-34110 and fix it if it is affected.

What it is: CVE-2021-34110 is a high-severity vulnerability in n/a, published on 8 Jul 2021. 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-2021-34110 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-2021-34110/ (Markdown: https://insights.sbomify.com/CVE-2021-34110/index.md)
```

## Sources

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

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