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

> Unprivileged local users can escalate privileges to SYSTEM by modifying the service binary path due to insecure default permissions.

- **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:** 11 Oct 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-xcw5-623c-7f4p

## What is CVE-2018-12441?

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

### Official description

The CorsairService Service in Corsair Utility Engine is installed with insecure default permissions, which allows unprivileged local users to execute arbitrary commands via modification of the CorsairService BINARY_PATH_NAME, leading to complete control of the affected system. The issue exists due to the Windows "Everyone" group being granted SERVICE_ALL_ACCESS permissions to the CorsairService Service.

Weakness: CWE-276 (Incorrect Default Permissions)

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

It affects 1 product.


Products: Corsair Corsair Utility Engine.

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

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

## Is CVE-2018-12441 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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