# CVE-2021-32022: Privilege escalation in BlackBerry Protect for Windows

> A low-privileged attacker can exploit a CEF RPC vulnerability to execute code with admin rights and delete local data in BlackBerry Protect for Windows.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **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:** 10 Nov 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-qpcm-p96p-jr73

## What is CVE-2021-32022?

CVE-2021-32022 is a medium-severity vulnerability in BlackBerry Protect for Windows, published on 10 Nov 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A low privileged delete vulnerability using CEF RPC server of BlackBerry Protect for Windows version(s) versions 1574 and earlier could allow an attacker to potentially execute code in the context of a BlackBerry Cylance service that has admin rights on the system and gaining the ability to delete data from the local system.

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

It affects 1 product.


Products: Blackberry Protect.

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

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

## Is CVE-2021-32022 being exploited?

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

## Other vulnerabilities in BlackBerry Protect for Windows

- [CVE-2021-32021](https://insights.sbomify.com/CVE-2021-32021/): Denial of service in BlackBerry Protect for Windows (high 7.8)
- [CVE-2021-32023](https://insights.sbomify.com/CVE-2021-32023/): Privilege escalation in BlackBerry Protect for Windows (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-32022 is a medium-severity vulnerability in BlackBerry Protect for Windows, published on 10 Nov 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-32022 in the wild and no public exploit code.

Affected product: BlackBerry Protect for Windows. 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-32022/ (Markdown: https://insights.sbomify.com/CVE-2021-32022/index.md)
```

## Sources

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

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