ghsa-cj47-qj6g-x7r4
Vulnerability from github
Published
2025-03-20 12:32
Modified
2025-03-21 03:30
Severity ?
Summary
vLLM allows Remote Code Execution by Pickle Deserialization via AsyncEngineRPCServer() RPC server entrypoints
Details
vllm-project vllm version 0.6.0 contains a vulnerability in the AsyncEngineRPCServer() RPC server entrypoints. The core functionality run_server_loop() calls the function _make_handler_coro(), which directly uses cloudpickle.loads() on received messages without any sanitization. This can result in remote code execution by deserializing malicious pickle data.
{ "affected": [ { "package": { "ecosystem": "PyPI", "name": "vllm" }, "ranges": [ { "events": [ { "introduced": "0" }, { "last_affected": "0.6.0" } ], "type": "ECOSYSTEM" } ] } ], "aliases": [ "CVE-2024-9053" ], "database_specific": { "cwe_ids": [ "CWE-502", "CWE-78" ], "github_reviewed": true, "github_reviewed_at": "2025-03-21T03:30:51Z", "nvd_published_at": "2025-03-20T10:15:46Z", "severity": "CRITICAL" }, "details": "vllm-project vllm version 0.6.0 contains a vulnerability in the AsyncEngineRPCServer() RPC server entrypoints. The core functionality run_server_loop() calls the function _make_handler_coro(), which directly uses cloudpickle.loads() on received messages without any sanitization. This can result in remote code execution by deserializing malicious pickle data.", "id": "GHSA-cj47-qj6g-x7r4", "modified": "2025-03-21T03:30:51Z", "published": "2025-03-20T12:32:50Z", "references": [ { "type": "ADVISORY", "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-9053" }, { "type": "PACKAGE", "url": "https://github.com/vllm-project/vllm" }, { "type": "WEB", "url": "https://huntr.com/bounties/75a544f3-34a3-4da0-b5a3-1495cb031e09" } ], "schema_version": "1.4.0", "severity": [ { "score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ], "summary": "vLLM allows Remote Code Execution by Pickle Deserialization via AsyncEngineRPCServer() RPC server entrypoints" }
Loading...
Loading...
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.