Authenticated command injection via unsanitized Kubernetes token
Published Mar 16, 2023 · Updated Feb 25, 2025
Command injection in JumpServer Koko before 2.28.8 allows remote authenticated users to execute commands through a Kubernetes token. Koko's Kubernetes connection handling embeds the supplied token in a shell command without neutralizing command separators, causing token text to be interpreted as commands. Exploitation requires high privileges, user interaction, and access to a configured Kubernetes asset; injected commands can modify files or interrupt the Koko container.
Summary
What happened
Command injection in JumpServer Koko before 2.28.8 allows remote authenticated users to execute commands through a Kubernetes token. Koko's Kubernetes connection handling embeds the supplied token in a shell command without neutralizing command separators, causing token text to be interpreted as commands. Exploitation requires high privileges, user interaction, and access to a configured Kubernetes asset; injected commands can modify files or interrupt the Koko container.
The record
- CVE
- CVE-2023-28110
- Published
- Mar 16, 2023
- Updated
- Feb 25, 2025
- Vendor
- JumpServer
- Product
- JumpServer
- Classifications
- CWE-77, T1059
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Mar 16, 2023CVE publishedPublication date reported by the CVE source.
- Feb 25, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.28.8
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Malicious Kubernetes token command-injection proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo