# CVE-2018-6651: Cross-site request forgery in n/a

> Insufficient Origin header validation in Parsec allows remote attackers to bypass access restrictions and gain full control of the victim's computer.

- **Severity:** High 8.8 (`CVSS:3.0/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 Feb 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-g952-h9rv-wc2r

## What is CVE-2018-6651?

CVE-2018-6651 is a high-severity vulnerability in n/a, published on 5 Feb 2018. 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

In the uncurl_ws_accept function in uncurl.c in uncurl before 0.07, as used in Parsec before 140-3, insufficient Origin header validation (accepting an arbitrary substring match) for WebSocket API requests allows remote attackers to bypass intended access restrictions. In Parsec, this means full control over the victim's computer.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2018-6651?

It affects 2 products.


Products: Parsecgaming Parsec, Uncurl Project Uncurl.

## How do I fix CVE-2018-6651?

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

## Is CVE-2018-6651 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-6634](https://insights.sbomify.com/CVE-2018-6634/): Auth bypass in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-6651 and fix it if it is affected.

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

## Sources

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

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