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

> A low-privileged user can escalate privileges to SYSTEM by modifying service configurations or overwriting binaries in TeraRecon AQNetClient.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Sep 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-jm93-wj83-qcv7

## What is CVE-2021-35508?

CVE-2021-35508 is a high-severity vulnerability in n/a, published on 1 Sep 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

NMSAccess32.exe in TeraRecon AQNetClient 4.4.13 allows attackers to execute a malicious binary with SYSTEM privileges via a low-privileged user account. To exploit this, a low-privileged user must change the service configuration or overwrite the binary service.

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

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

It affects 1 product.


Products: Terarecon Aquariusnet.

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

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

## Is CVE-2021-35508 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-35508 is a high-severity vulnerability in n/a, published on 1 Sep 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-35508 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-35508/ (Markdown: https://insights.sbomify.com/CVE-2021-35508/index.md)
```

## Sources

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

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