# CVE-2024-35214: Vulnerability in CylanceOPTICS Windows Installer Package Impacts CylanceOPTICS for Windows

> An attacker can tamper with the installer to uninstall CylanceOPTICS, bypassing endpoint security protections.

- **Severity:** High 7.1 (`CVSS:4.0/AV:L/AC:H/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Aug 2024
- **Updated:** 29 Sep 2024
- **Also known as:** GHSA-4qxp-c58r-4xg9

## What is CVE-2024-35214?

CVE-2024-35214 is a high-severity vulnerability in BlackBerry CylanceOPTICS for Windows, published on 20 Aug 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A tampering vulnerability in the CylanceOPTICS Windows Installer Package of CylanceOPTICS for Windows version 3.2 and 3.3 could allow an attacker to potentially uninstall CylanceOPTICS from a system thereby leaving it with only the protection of CylancePROTECT.

Weakness: CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

## Which versions are affected by CVE-2024-35214?


## How do I fix CVE-2024-35214?

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

## Is CVE-2024-35214 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-35214 and fix it if it is affected.

What it is: CVE-2024-35214 is a high-severity vulnerability in BlackBerry CylanceOPTICS for Windows, published on 20 Aug 2024. 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-2024-35214 in the wild and no public exploit code.

Affected product: BlackBerry CylanceOPTICS 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-2024-35214/ (Markdown: https://insights.sbomify.com/CVE-2024-35214/index.md)
```

## Sources

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

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