# CVE-2023-32232: Privilege escalation in n/a

> A standard user can escape a visible elevated installer window to gain SYSTEM privileges, allowing arbitrary code execution on Windows systems.

- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Jul 2023
- **Updated:** 24 Oct 2024
- **Also known as:** GHSA-4mq4-7fv7-xw62

## What is CVE-2023-32232?

CVE-2023-32232 is a critical vulnerability in n/a, published on 25 Jul 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in Vasion PrinterLogic Client for Windows before 25.0.0.836. During client installation and repair, a PrinterLogic binary is called by the installer to configure the device. This window is not hidden, and is running with elevated privileges. A standard user can break out of this window, obtaining a full SYSTEM command prompt window. This results in complete compromise via arbitrary SYSTEM code execution (elevation of privileges).

## Which versions are affected by CVE-2023-32232?

It affects 1 product.


Products: Vasion Printerlogic Client.

## How do I fix CVE-2023-32232?

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

## Is CVE-2023-32232 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-32231](https://insights.sbomify.com/CVE-2023-32231/): Privilege escalation in n/a (critical 9.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-32232 and fix it if it is affected.

What it is: CVE-2023-32232 is a critical vulnerability in n/a, published on 25 Jul 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-32232 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-2023-32232/ (Markdown: https://insights.sbomify.com/CVE-2023-32232/index.md)
```

## Sources

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

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