# CVE-2018-10722: Privilege escalation in n/a

> An unprivileged local user can escalate to SYSTEM privileges via symlink attacks in the log folder of CylancePROTECT.

- **Severity:** High 7.8 (`CVSS:3.0/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:** 4 May 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-c4cc-f3xf-qqpw

## What is CVE-2018-10722?

CVE-2018-10722 is a high-severity vulnerability in n/a, published on 4 May 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In Cylance CylancePROTECT before 1470, an unprivileged local user can obtain SYSTEM privileges because users have Modify access to the %PROGRAMFILES%\Cylance\Desktop\log folder, the CyUpdate process grants users Modify access to new files created in this folder, and a new file can be a symlink chain to a pathname of an arbitrary DLL that CyUpdate uses.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

## Which versions are affected by CVE-2018-10722?

It affects 1 product.


Products: Cylance Cylanceprotect.

## How do I fix CVE-2018-10722?

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

## Is CVE-2018-10722 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-10722 and fix it if it is affected.

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

## Sources

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

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