# CVE-2023-47250: Missing authorization in n/a

> Authenticated attackers can access other users' X11 desktops and inject keystrokes due to broken access control on server sockets.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Nov 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-wh59-6mh7-85h4

## What is CVE-2023-47250?

CVE-2023-47250 is a high-severity missing authorization vulnerability in n/a, published on 22 Nov 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In mprivacy-tools before 2.0.406g in m-privacy TightGate-Pro Server, broken Access Control on X11 server sockets allows authenticated attackers (with access to a VNC session) to access the X11 desktops of other users by specifying their DISPLAY ID. This allows complete control of their desktop, including the ability to inject keystrokes and perform a keylogging attack.

Weakness: CWE-276 (Incorrect Default Permissions)

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

It affects 3 products.


Products: M-Privacy Mprivacy-Tools, M-Privacy Rsbac-Policy-Tgpro, M-Privacy Tightgatevnc.

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

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

## Is CVE-2023-47250 being exploited?

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

Public exploit code:

- Controlled break-fix demo and Bash automation for CVE-2023-47250, an X11 session access-control vulnerability (Kali Linux). (github_poc): https://github.com/christinasm1th/CVE-2023-47250-break-fix

## Other vulnerabilities in n/a

- [CVE-2023-47251](https://insights.sbomify.com/CVE-2023-47251/): Path traversal in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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