GHSA-59PJ-5774-XP3F
Legacy LMCacheServer accepts unvalidated TCP message lengths, enabling denial of service
Texto original en inglés · Ver en español
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Remediación | Parche 0.5.7.post1 | lmcache · -6 d desde divulgación | |
| Divulgación | Publicada | GHSA-59PJ-5774-XP3F divulgada | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
Summary
The legacy in-process `LMCacheServer` trusts a client-controlled TCP payload length without validation. An unauthenticated network peer can declare a very large payload and then send insufficient data, causing the server to block while waiting for the remainder. Repeating this across connections can exhaust server threads and other resources, resulting in denial of service.
Details
In `lmcache/v1/server/__main__.py`, the server deserializes `ClientMetaMessage` and passes `meta.length` directly to `receive_all()` for PUT requests. The implementation does not enforce a maximum payload length or a per-connection socket timeout. It also creates an unbounded thread for every accepted connection. A remote peer that can reach the legacy TCP service can therefore keep many handler threads blocked indefinitely with incomplete payloads.
This implementation belongs to LMCache's deprecated in-process mode. It was removed by PR #5785 https://github.com/LMCache/LMCache/pull/5785.
Proof of concept
In an isolated test environment, connect to the legacy TCP server, send a valid PUT header whose length field declares a large payload, and then send only a small portion of that payload while keeping the socket open. The corresponding handler thread remains blocked waiting for the declared number of bytes. Opening multiple such connections causes the server to accumulate blocked threads and resource usage.
Impact
If the legacy TCP service is reachable, an unauthenticated attacker can exhaust server threads, file descriptors, and memory, degrading availability or making the cache service unresponsive.
Resolution
Upgrade to MP mode. The vulnerable custom TCP server is part of the deprecated in-process mode and is not used by MP mode. The legacy server was removed in PR #5785 https://github.com/LMCache/LMCache/pull/5785; it is absent from v0.5.7rc1 and later prereleases.
Incluye detalles técnicos publicados por el investigador. Úselos solo para validar y corregir sus propios sistemas.
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
pypilmcache |
Corregida | 0.5.7.post1 | -6 d | 0.5.7.post1 no afectada |
0.5.7.post10.5.7Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://github.com/LMCache/LMCache/security/advisories/GHSA-59pj-5774-xp3fLas referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
