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

> Local unprivileged users can replace a service executable with incorrect permissions to execute arbitrary code with LocalSystem privileges.

- **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:** 6 Aug 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-q7qw-9796-gjgr

## What is CVE-2021-35312?

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

### Official description

A vulnerability was found in CIR 2000 / Gestionale Amica Prodigy v1.7. The Amica Prodigy's executable "RemoteBackup.Service.exe" has incorrect permissions, allowing a local unprivileged user to replace it with a malicious file that will be executed with "LocalSystem" privileges.

Weakness: CWE-276 (Incorrect Default Permissions)

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

It affects 1 product.


Products: Gestionaleamica Amica Prodigy.

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

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

## Is CVE-2021-35312 being exploited?

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

Public exploit code:

- Amica Prodigy 1.7 - Privilege Escalation (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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