# CVE-2023-43651: Remote code execution on the host system via MongoDB shell in jumpserver

> Authenticated users can execute arbitrary commands via MongoDB sessions in JumpServer, leading to remote code execution and potential root privilege escalation.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/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:** Yes
- **Published:** 27 Sep 2023
- **Updated:** 25 Mar 2025
- **Also known as:** GHSA-4r5x-x283-wm96

## What is CVE-2023-43651?

CVE-2023-43651 is a high-severity command injection vulnerability in jumpserver, published on 27 Sep 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

JumpServer is an open source bastion host. An authenticated user can exploit a vulnerability in MongoDB sessions to execute arbitrary commands, leading to remote code execution. This vulnerability may further be leveraged to gain root privileges on the system. Through the WEB CLI interface provided by the koko component, a user logs into the authorized mongoDB database and exploits the MongoDB session to execute arbitrary commands. This vulnerability has been addressed in versions 2.28.20 and 3.7.1. Users are advised to upgrade. There are no known workarounds for this vulnerability.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

4 open source packages ship an affected version, including github.com/jumpserver/koko. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/jumpserver/koko` | Go | From 2.0.0 | 2.28.20 |
| `github.com/jumpserver/koko` | Go | From 2.0.0 | 2.28.20 |
| `github.com/jumpserver/koko` | Go | From 3.0.0 | 3.7.1 |
| `github.com/jumpserver/koko` | Go | From 3.0.0 | 3.7.1 |

Products: Fit2cloud Jumpserver.

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

Upgrade github.com/jumpserver/koko to a fixed version for your release line: 2.28.20 or 3.7.1.

## Is CVE-2023-43651 being exploited?

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

## 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-43651 and fix it if it is affected.

What it is: CVE-2023-43651 is a high-severity command injection vulnerability in jumpserver, published on 27 Sep 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-43651 exists.

Affected packages and fixed versions:
- github.com/jumpserver/koko (Go): affected from 2.0.0; fixed in 2.28.20
- github.com/jumpserver/koko (Go): affected from 2.0.0; fixed in 2.28.20
- github.com/jumpserver/koko (Go): affected from 3.0.0; fixed in 3.7.1
- github.com/jumpserver/koko (Go): affected from 3.0.0; fixed in 3.7.1

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

## Sources

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

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