[Kimi VS Code] Command Injection in publish scripts vsix-publish.js and ovsx-publish.js
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| MoonshotAI | kimi-agent-sdk | affected |
|
No data.
No data.
| Vendor | Product | Versions |
|---|---|---|
| Moonshotai | Kimi-agent-sdk | — |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.135% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Moonshotai
Moonshotai kimi-agent-sdk |
|
| Vendors & Products |
Moonshotai
Moonshotai kimi-agent-sdk |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Kimi Agent SDK is a set of libraries that expose the Kimi Code (Kimi CLI) agent runtime in applications. The vsix-publish.js and ovsx-publish.js scripts pass filenames to execSync() as shell command strings. Prior to version 0.1.6, filenames containing shell metacharacters like $(cmd) could execute arbitrary commands. Note: This vulnerability exists only in the repository's development scripts. The published VSCode extension does not include these files and end users are not affected. This is fixed in version 0.1.6 by replacing execSync with execFileSync using array arguments. As a workaround, ensure .vsix files in the project directory have safe filenames before running publish scripts. | |
| Title | [Kimi VS Code] Command Injection in publish scripts vsix-publish.js and ovsx-publish.js | |
| Weaknesses | CWE-77 | |
| References |
| |
| Metrics |
cvssV3_1
|