# CVE-2022-24286: Privilege escalation in n/a

> Local attackers can escalate privileges to system level by exploiting insecure named pipe permissions and lack of authentication in Acer QuickAccess.

- **Severity:** High 7.8 (`CVSS:3.1/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:** 8 Mar 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-m3r3-qchc-m9xx

## What is CVE-2022-24286?

CVE-2022-24286 is a high-severity vulnerability in n/a, published on 8 Mar 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Acer QuickAccess 2.01.300x before 2.01.3030 and 3.00.30xx before 3.00.3038 contains a local privilege escalation vulnerability. The user process communicates with a service of system authority through a named pipe. In this case, the Named Pipe is also given Read and Write rights to the general user. In addition, the service program does not verify the user when communicating. A thread may exist with a specific command. When the path of the program to be executed is sent, there is a local privilege escalation in which the service program executes the path with system privileges.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2022-24286?

It affects 1 product.


Products: Acer Quickaccess.

## How do I fix CVE-2022-24286?

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

## Is CVE-2022-24286 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-24286 and fix it if it is affected.

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

## Sources

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

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