# CVE-2017-7884: Privilege escalation in n/a

> Local authenticated users can escalate privileges to SYSTEM by replacing the service executable due to insecure default file permissions.

- **Severity:** High 8.4 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 16 Jun 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-x543-885p-w95x

## What is CVE-2017-7884?

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

### Official description

In Adam Kropelin adk0212 APC UPS Daemon through 3.14.14, the default installation of APCUPSD allows a local authenticated, but unprivileged, user to run arbitrary code with elevated privileges by replacing the service executable apcupsd.exe with a malicious executable that will run with SYSTEM privileges at startup. This occurs because of "RW NT AUTHORITY\Authenticated Users" permissions for %SYSTEMDRIVE%\apcupsd\bin\apcupsd.exe.

Weakness: CWE-427 (Uncontrolled Search Path Element)

## Which versions are affected by CVE-2017-7884?

It affects 1 product.


Products: Apcupsd Apc Ups Daemon.

## How do I fix CVE-2017-7884?

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

## Is CVE-2017-7884 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-7884 and fix it if it is affected.

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

## Sources

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

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