Kiteworks Core Command Execution through Configuration Injection
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Kiteworks | Core | unknown |
|
No data.
| Vendor | Product | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Kiteworks | Core |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.125% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Accellion
Accellion kiteworks |
|
| CPEs | cpe:2.3:a:accellion:kiteworks:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Accellion
Accellion kiteworks |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Kiteworks
Kiteworks core |
|
| Vendors & Products |
Kiteworks
Kiteworks core |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | In multi-node deployments, an attacker who had already obtained code execution on one appliance node could submit a value through an internal cluster interface that was written into monitoring configuration on another node without sufficient validation, potentially allowing OS commands to be executed there. Execution was limited to an unprivileged service account on that node. | |
| Title | Kiteworks Core Command Execution through Configuration Injection | |
| Weaknesses | CWE-93 | |
| References |
| |
| Metrics |
cvssV3_1
|