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

> Local attackers can escalate privileges by replacing executables in the PCProtect directory due to overly permissive file permissions.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 Sep 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-6v2j-64px-rm5x

## What is CVE-2018-17776?

CVE-2018-17776 is a high-severity vulnerability in n/a, published on 28 Sep 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

PCProtect Anti-Virus v4.8.35 has "Everyone: (F)" permission for %PROGRAMFILES(X86)%\PCProtect, which allows local users to gain privileges by replacing an executable file with a Trojan horse.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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

It affects 1 product.


Products: Pcprotect Antivirus.

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

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

## Is CVE-2018-17776 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-17776 exists.

Public exploit code:

- PCProtect 4.8.35 - Privilege Escalation (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2019-16913](https://insights.sbomify.com/CVE-2019-16913/): Privilege escalation in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-17776 is a high-severity vulnerability in n/a, published on 28 Sep 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-17776 exists.

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-17776/ (Markdown: https://insights.sbomify.com/CVE-2018-17776/index.md)
```

## Sources

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

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