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

> Local attackers can escalate privileges on systems running WithSecure endpoint security products.

- **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:** 20 Nov 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-9cp2-fvjp-4q3f

## What is CVE-2023-47172?

CVE-2023-47172 is a high-severity vulnerability in n/a, published on 20 Nov 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Certain WithSecure products allow Local Privilege Escalation. This affects WithSecure Client Security 15, WithSecure Server Security 15, WithSecure Email and Server Security 15, and WithSecure Elements Endpoint Protection 17 and later.

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

It affects 4 products.


Products: Withsecure Client Security, Withsecure Elements Endpoint Protection, Withsecure Email and Server Security, Withsecure Server Security.

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

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

## Is CVE-2023-47172 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-4454](https://insights.sbomify.com/CVE-2024-4454/): WithSecure Elements Endpoint Protection Link Following Local Privilege Escalation Vulnerability (high 7.3)
- [CVE-2024-23764](https://insights.sbomify.com/CVE-2024-23764/): Privilege escalation in n/a (medium 6.7)

## Fix prompt for AI coding agents

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

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

## Sources

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

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