What is CVE-2023-43651?

CVE-2023-43651 is a medium-severity code injection vulnerability in github.com/jumpserver/koko (go), affecting versions >= 2.0.0, < 2.28.20. It is fixed in 2.28.20, 3.7.1. Untrusted input is evaluated as executable code within the application's runtime environment.

How severe is CVE-2023-43651?

CVE-2023-43651 has a CVSS score of 6.4 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of github.com/jumpserver/koko are affected by CVE-2023-43651?

github.com/jumpserver/koko (go) versions >= 2.0.0, < 2.28.20 is affected.

Is there a fix for CVE-2023-43651?

Yes. CVE-2023-43651 is fixed in 2.28.20, 3.7.1. Upgrade to this version or later.

Is CVE-2023-43651 exploitable, and should I be worried?

Whether CVE-2023-43651 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2023-43651 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2023-43651?

Upgrade: github.com/jumpserver/koko to 2.28.20 or later, github.com/jumpserver/koko to 3.7.1 or later.

CVE-2023-43651 in github.com/jumpserver/koko

Q: How severe is CVE-2023-43651?

CVE-2023-43651 has a CVSS score of 6.4 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of github.com/jumpserver/koko are affected by CVE-2023-43651?

github.com/jumpserver/koko (go) versions >= 2.0.0, < 2.28.20 is affected.

Q: Is there a fix for CVE-2023-43651?

Yes. CVE-2023-43651 is fixed in 2.28.20, 3.7.1. Upgrade to this version or later.

Q: Is CVE-2023-43651 exploitable, and should I be worried?

Whether CVE-2023-43651 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2023-43651 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2023-43651?

Upgrade: github.com/jumpserver/koko to 2.28.20 or later, github.com/jumpserver/koko to 3.7.1 or later.

Summary

Jumpserver Koko vulnerable to remote code execution on the host system via MongoDB shell

Details

Through the WEB CLI interface provided by koko, a user logs into the authorized mongoDB database and exploits the MongoDB session to execute arbitrary commands.

admin> const { execSync } = require("child_process")
admin> console.log(execSync("id; hostname;").toString())
uid=0(root) gid=0(root) groups=0(root)
jms_koko
admin>

Workarounds

It is recommended to upgrade the safe versions.

After upgrade, you can use the same method to check whether the vulnerability is fixed.

admin> console.log(execSync("id; hostname;").toString())
/bin/sh: line 1: /bin/hostname: Permission denied

References

Thanks for Oskar Zeino-Mahmalat of Sonar found and report this vulnerability

Impact

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 host system.

Untrusted input is evaluated as executable code within the application's runtime environment. Typical impact: arbitrary code execution within the application's privilege context.

CVE-2023-43651 has a CVSS score of 6.4 (Medium). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.28.20, 3.7.1); upgrading removes the vulnerable code path.

Affected versions

github.com/jumpserver/koko (>= 2.0.0, < 2.28.20) github.com/jumpserver/koko (>= 3.0.0, < 3.7.1)

Security releases

github.com/jumpserver/koko → 2.28.20 (go) github.com/jumpserver/koko → 3.7.1 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Safe versions:

v2.28.20
v3.7.1

Frequently Asked Questions

What is CVE-2023-43651? CVE-2023-43651 is a medium-severity code injection vulnerability in github.com/jumpserver/koko (go), affecting versions >= 2.0.0, < 2.28.20. It is fixed in 2.28.20, 3.7.1. Untrusted input is evaluated as executable code within the application's runtime environment.
How severe is CVE-2023-43651? CVE-2023-43651 has a CVSS score of 6.4 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of github.com/jumpserver/koko are affected by CVE-2023-43651? github.com/jumpserver/koko (go) versions >= 2.0.0, < 2.28.20 is affected.
Is there a fix for CVE-2023-43651? Yes. CVE-2023-43651 is fixed in 2.28.20, 3.7.1. Upgrade to this version or later.
Is CVE-2023-43651 exploitable, and should I be worried? Whether CVE-2023-43651 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2023-43651 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2023-43651?
- Upgrade github.com/jumpserver/koko to 2.28.20 or later
- Upgrade github.com/jumpserver/koko to 3.7.1 or later