# CVE-2020-9332: Privilege escalation in n/a

> A local attacker can escalate privileges by sending crafted IoCtl codes to the FabulaTech USB for Remote Desktop driver.

- **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:** 17 Jun 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-pjxp-vfpq-9869

## What is CVE-2020-9332?

CVE-2020-9332 is a high-severity vulnerability in n/a, published on 17 Jun 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

ftusbbus2.sys in FabulaTech USB for Remote Desktop through 2020-02-19 allows privilege escalation via crafted IoCtl code related to a USB HID device.

## Which versions are affected by CVE-2020-9332?

It affects 1 product.


Products: Fabulatech Usb for Remote Desktop.

## How do I fix CVE-2020-9332?

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

## Is CVE-2020-9332 being exploited?

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

Public exploit code:

- https://github.com/Sentinel-One/CVE-2020-9332 (github_poc): https://github.com/Sentinel-One/CVE-2020-9332

## Other vulnerabilities in n/a

- [CVE-2023-2871](https://insights.sbomify.com/CVE-2023-2871/): FabulaTech USB for Remote Desktop IoControlCode 0x220408 null pointer dereference (low 3.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-9332 and fix it if it is affected.

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

## Sources

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

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