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

> A low-privileged user can escalate to root privileges in Oracle Solaris CDE by double-clicking a maliciously crafted printer icon.

- **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:** 31 Oct 2022
- **Updated:** 6 May 2025
- **Also known as:** GHSA-5x3r-56hw-m9mp

## What is CVE-2022-43752?

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

### Official description

Oracle Solaris version 10 1/13, when using the Common Desktop Environment (CDE), is vulnerable to a privilege escalation vulnerability. A low privileged user can escalate to root by crafting a malicious printer and double clicking on the the crafted printer's icon.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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

It affects 1 product.


Products: Common Desktop Environment Project  Common Desktop Environment.

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

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

## Is CVE-2022-43752 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-43752 is a high-severity vulnerability in n/a, published on 31 Oct 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-43752 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-2022-43752/ (Markdown: https://insights.sbomify.com/CVE-2022-43752/index.md)
```

## Sources

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

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