Caching doesn’t work the way the bug reporter implies. Caches are shared (at least across the enterprise), but its key is always a function of the input before it. We achieved significant savings simply by moving everything that varies across individuals out of the system prompt so every session starts from a cache point. For example you never want your system prompt to start with the time that the session started. M…
Hash functions necesarily have collisions. Also, it is perfectly possible to introduce bugs in the hash function (hash inputs, hash function itself) that allows cross account contamination.
Potential session/cache leakage between workspace instances or consumer accounts
71–80 of 151 posts
Re: Potential session/cache leakage between workspace instances or consumer accounts
#72Re: Potential session/cache leakage between workspace instances or consumer accounts
#73This seems like a hallucination.
Re: Potential session/cache leakage between workspace instances or consumer accounts
#74Using a throwaway account for obvious reasons, but I’m very involved in this space using LLMs from multiple providers. I’m aware of at least two instances in which the intermediate infrastructure “swapped” responses, once impacting Claude models and once impacting GPT models, from two different providers. One gave us a proper postmortem in which their API gateway was incorrectly handling HTTP 100 status codes, puttin…
Every time you multiplex requests from multiple clients onto one upstream connection, you are probably vulnerable to this, because (despite its superficial simplicity) HTTP is just too complex to reliably match the requests and responses to upstream.
For example a desync can be triggered in some systems by having more than one Content-Length header, by mixing Content-Length with chunked encoding, or by passing an HTTP/2 header called Content-Length that doesn't match the actual content length.
Here's a DEF CON talk (6 years ago) on this topic: https://www.youtube.com/watch?v=w-eJM2Pc0KI
The same attack has been applied to SMTP by messing up the line endings surrounding the end-of-message delimiter, where it's called SMTP smuggling. It may also apply to other protocols.
Re: Potential session/cache leakage between workspace instances or consumer accounts
#75Using a throwaway account for obvious reasons, but I’m very involved in this space using LLMs from multiple providers. I’m aware of at least two instances in which the intermediate infrastructure “swapped” responses, once impacting Claude models and once impacting GPT models, from two different providers. One gave us a proper postmortem in which their API gateway was incorrectly handling HTTP 100 status codes, puttin…
Re: Potential session/cache leakage between workspace instances or consumer accounts
#76Re: Potential session/cache leakage between workspace instances or consumer accounts
#77Earlier quoted context omitted.
Not sure the relevance of this comment, but normally if someone built a classifier that bad they’d be fired. Anthropic obviously thinks they have some monopoly power they can use to foist garbage on consumers, I think they don’t.
If people are complaining about Anthropic (on an only-vaguely related thread) rather than simply switching to a suitable competitor, then Anthropic clearly has some 'monopoly' power over the specific capabilities the complainer wants from them.
Re: Potential session/cache leakage between workspace instances or consumer accounts
#78Re: Potential session/cache leakage between workspace instances or consumer accounts
#79Earlier quoted context omitted.
[flagged]
Curious why you feel that way about Dario?
Dario might not be a literal idiot, but he might strongly benefit from training a model to do strategic thinking for Anthropic.
Re: Potential session/cache leakage between workspace instances or consumer accounts
#80I’ve been seeing this in Gemini in the past few days. Often during a prompt with a reasonably large input set, I’ll get answers that appear to belong to someone else. It may be trigger hallucination, but it seems like it may be cache collisions or something else. I’ve not seen anything to suggest private information is leaking, but it’s disconcerting to be researching something and then get what appears to be a math…
That is when it bothers to respond instead of just sending back an 1099 error code