Range cache poisoning
Named by 2 kept items in this workspace.
Search every workspace for Range cache poisoning. It matches the name as written, so it can find other things that share it.
The items that name it 2
Technique exploiting RANGE responses sent without a 206 status code, enabling potential cache poisoning via front-end reassembly or context-aware escaping.
Technique exploiting RANGE responses sent without a 206 status code that could be incorrectly cached, enabling exploitation via front-end reassembly or context-aware escaping; described as an unconfirmed research lead
All techniques in this workspace.