# CVE-2022-36601: Auth bypass in n/a

> Unauthenticated attackers can exploit the open Eclipse TCF debug interface to gain root privileges and execute arbitrary commands on JasMiner X4 Servers.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 1 Sep 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-6447-c9hr-5hv5

## What is CVE-2022-36601?

CVE-2022-36601 is a critical authentication bypass vulnerability in n/a, published on 1 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Eclipse TCF debug interface in JasMiner-X4-Server-20220621-090907 and below is open on port 1534. This issue allows unauthenticated attackers to gain root privileges on the affected device and access sensitive data or execute arbitrary commands.

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

It affects 1 product.


Products: Jinglemining Jasminer X4 Server Firmware.

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

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

## Is CVE-2022-36601 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-36601 is a critical authentication bypass vulnerability in n/a, published on 1 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-36601 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-2022-36601/ (Markdown: https://insights.sbomify.com/CVE-2022-36601/index.md)
```

## Sources

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

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