# CVE-2023-42442: JumpServer session replays download without authentication

> Attackers can download session replays without authentication due to broken permission controls in the JumpServer API.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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:** 15 Sep 2023
- **Updated:** 25 Sep 2024
- **Also known as:** GHSA-633x-3f4f-v9rw

## What is CVE-2023-42442?

CVE-2023-42442 is a high-severity missing authorization vulnerability in jumpserver, published on 15 Sep 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

JumpServer is an open source bastion host and a professional operation and maintenance security audit system. Starting in version 3.0.0 and prior to versions 3.5.5 and 3.6.4, session replays can download without authentication. Session replays stored in S3, OSS, or other cloud storage are not affected. The api `/api/v1/terminal/sessions/` permission control is broken and can be accessed anonymously. SessionViewSet permission classes set to `[RBACPermission | IsSessionAssignee]`, relation is or, so any permission matched will be allowed. Versions 3.5.5 and 3.6.4 have a fix. After upgrading, visit the api `$HOST/api/v1/terminal/sessions/?limit=1`. The expected http response code is 401 (`not_authenticated`).

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Fit2cloud Jumpserver.

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

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

## Is CVE-2023-42442 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-42442 exists.

Public exploit code:

- JumpServer 堡垒机未授权综合漏洞利用, Exploit for CVE-2023-42442 / CVE-2023-42820 / RCE 2021 (github_poc): https://github.com/tarihub/blackjump
- https://github.com/HolyGu/CVE-2023-42442 (github_poc): https://github.com/HolyGu/CVE-2023-42442
- CVE-2023-42442 JumpServer Session 录像任意下载漏洞 (github_poc): https://github.com/C1ph3rX13/CVE-2023-42442
- JumpServer > 3.6.4 - Information Disclosure (nuclei): http/cves/2023/CVE-2023-42442.yaml

## Other vulnerabilities in jumpserver

- [CVE-2024-40628](https://insights.sbomify.com/CVE-2024-40628/): Arbitrary File Read in Ansible Playbooks in Jumpserver (critical 10.0)
- [CVE-2024-40629](https://insights.sbomify.com/CVE-2024-40629/): Arbitrary File Write in Ansible Playbooks leads to RCE in Jumpserver (critical 10.0)
- [CVE-2024-29201](https://insights.sbomify.com/CVE-2024-29201/): JumpServer's insecure Ansible playbook validation leads to RCE in Celery (critical 10.0)
- [CVE-2024-29202](https://insights.sbomify.com/CVE-2024-29202/): JumpServer vulnerable to Jinja2 template injection in Ansible leads to RCE in Celery (critical 10.0)
- [CVE-2023-48193](https://insights.sbomify.com/CVE-2023-48193/): Security feature bypass in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-42442 is a high-severity missing authorization vulnerability in jumpserver, published on 15 Sep 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-42442 exists.

Affected product: jumpserver. 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-42442/ (Markdown: https://insights.sbomify.com/CVE-2023-42442/index.md)
```

## Sources

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

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