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

> Local attackers can escalate privileges on macOS via the inSyncDecommission component in Druva inSync.

- **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:** 11 Jul 2022
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-5rc3-9cqf-fhjx

## What is CVE-2021-36666?

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

### Official description

An issue was discovered in Druva 6.9.0 for MacOS, allows attackers to gain escalated local privileges via the inSyncDecommission.

Weakness: CWE-426 (Untrusted Search Path)

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

It affects 1 product.


Products: Druva Insync Client.

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

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

## Is CVE-2021-36666 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-36665](https://insights.sbomify.com/CVE-2021-36665/): Deserialization in n/a (high 7.8)
- [CVE-2021-36667](https://insights.sbomify.com/CVE-2021-36667/): Command injection in n/a (high 7.8)
- [CVE-2021-36668](https://insights.sbomify.com/CVE-2021-36668/): Open redirect in n/a (high 7.8)
- [CVE-2020-5752](https://insights.sbomify.com/CVE-2020-5752/): Path traversal in Druva inSync Windows Client (high 7.8)
- [CVE-2019-3999](https://insights.sbomify.com/CVE-2019-3999/): Command injection in Druva inSync Windows Client (high 7.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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