Tagged:
side-channel4 posts
-
Prompt Cache Timing Attacks: Side-Channel Leakage in LLM API Infrastructure
Major LLM providers cache prompt prefixes to reduce latency and cost — but shared cache infrastructure creates a timing side-channel. An attacker with access to a shared API key or multi-tenant deployment can measure whether a specific prefix is cached, leaking information about co-tenant system prompts and conversation context within the same cache namespace.
-
Side-Channel Attacks on LLM APIs: What Response Timing and Token Counts Reveal
How LLM API metadata — token counts, timing, and streaming patterns — leaks system prompt structure and model configuration to adversaries.
-
Cross-Tenant Contamination in LLM APIs: When Other Users' Context Leaks Into Your Session
Multi-tenant LLM deployments — shared inference infrastructure, KV cache reuse, batched requests — create subtle cross-tenant data exposure risks that differ from classical API security vulnerabilities. This post maps the threat surface unique to shared AI inference.
-
Adversarial Prompt Caching: Timing Attacks and Injection via Shared KV Caches
As LLM providers roll out shared prefix caching to cut inference costs, a new attack surface emerges: cache-timing side channels and cross-tenant injection vectors at the inference infrastructure layer.