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

> A standard user can escalate privileges to SYSTEM via DLL hijacking in the FTP module of Allegro Windows.

- **Severity:** High 7.1 (`CVSS:3.1/AC:L/AV:A/A:N/C:H/I:L/PR:N/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Dec 2021
- **Updated:** 30 May 2025
- **Also known as:** GHSA-jx3f-hj4m-h7p9

## What is CVE-2021-42110?

CVE-2021-42110 is a high-severity vulnerability in n/a, published on 8 Dec 2021. 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 Allegro Windows (formerly Popsy Windows) before 3.3.4156.1. A standard user can escalate privileges to SYSTEM if the FTP module is installed, because of DLL hijacking.

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

It affects 1 product.


Products: Allegro Allegro.

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

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

## Is CVE-2021-42110 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-43978](https://insights.sbomify.com/CVE-2021-43978/): Hardcoded credentials in n/a (high 7.1)

## Fix prompt for AI coding agents

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

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

## Sources

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

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