LightLLM through 1.2.0 Unauthenticated Remote Code Execution via NCCL PD RPyC Control Channel
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| ModelTC | LightLLM | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Modeltc | Lightllm |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: 1.2% (1.193% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Modeltc
Modeltc lightllm |
|
| Vendors & Products |
Modeltc
Modeltc lightllm |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | LightLLM through 1.2.0 contains a remote code execution vulnerability in the KV-transfer worker when started with --pd_trans_mode nccl, which exposes an unauthenticated RPyC control channel that deserializes attacker-supplied data. Attackers can send malicious pickled objects to the exposed RPyC ThreadedServer to execute arbitrary code with the privileges of the LightLLM service account. | |
| Title | LightLLM through 1.2.0 Unauthenticated Remote Code Execution via NCCL PD RPyC Control Channel | |
| Weaknesses | CWE-502 | |
| References |
|
|
| Metrics |
cvssV3_1
|