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

> Attackers can bypass UAC and access system files with admin privileges when Listary is configured to run as administrator.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Dec 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-2m67-46qp-5j9w

## What is CVE-2021-41066?

CVE-2021-41066 is a high-severity vulnerability in n/a, published on 14 Dec 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

An issue was discovered in Listary through 6. When Listary is configured as admin, Listary will not ask for permissions again if a user tries to access files on the system from Listary itself (it will bypass UAC protection; there is no privilege validation of the current user that runs via Listary).

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Bopsoft Listary.

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

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

## Is CVE-2021-41066 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-41065](https://insights.sbomify.com/CVE-2021-41065/): Privilege escalation in n/a (high 7.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-41066 is a high-severity vulnerability in n/a, published on 14 Dec 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2021-41066 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-41066/ (Markdown: https://insights.sbomify.com/CVE-2021-41066/index.md)
```

## Sources

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

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