# CVE-2024-41889: Other in PiTool

> Remote unauthenticated attackers can execute arbitrary code via WebSocket connections in Pimax VR software.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 5 Aug 2024
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-w762-77xf-823w

## What is CVE-2024-41889?

CVE-2024-41889 is a high-severity vulnerability in Pimax PiTool, published on 5 Aug 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Multiple Pimax products accept WebSocket connections from unintended endpoints. If this vulnerability is exploited, arbitrary code may be executed by a remote unauthenticated attacker.

Weakness: CWE-923 (Improper Restriction of Communication Channel to Intended Endpoints)

## Which versions are affected by CVE-2024-41889?

It affects 2 products.


Products: Pimax Pitool, Pimax Play.

## How do I fix CVE-2024-41889?

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

## Is CVE-2024-41889 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-41889 and fix it if it is affected.

What it is: CVE-2024-41889 is a high-severity vulnerability in Pimax PiTool, published on 5 Aug 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-41889 in the wild and no public exploit code.

Affected product: Pimax PiTool. 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-2024-41889/ (Markdown: https://insights.sbomify.com/CVE-2024-41889/index.md)
```

## Sources

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

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