Repository navigation
docs(session): name cross-tenant cookie poisoning as the __Host- prefix's stakes - #20
Merged
Merged
Conversation
…ix's stakes The missing-__Host- bullet said a subdomain "can override the cookie" but never named the concrete blast radius, which is exactly what a Staff-level interviewer would probe on. Ties it explicitly to the cookie-tossing attack technique already in this doc (technique 8) and names the multi-tenant-SaaS consequence: a compromised or malicious tenant subdomain can poison the cookie for a different tenant's origin.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
__Host-bullet in12-authentication-session.mdsaid a subdomain "can override the cookie" but never named the concrete consequence.Note: kept the framing to what
__Host-actually defends against (browser-enforced cookie scoping / cookie tossing), not the separate server-side HTTP Host-header-trust vulnerability class covered in25-http-host-header.md-- those are different bug classes and conflating them would misattribute the control.Test plan
pytest tests/-- 11/11 passed.https://claude.ai/code/session_011f1KhQCYiUUPFKco7pguLC