Vary header cache key collision from missing delimiter
When a cached view varies on multiple headers, the values of those headers are concatenated together in the cache key. There is no delimiter, meaning the cache keys could overlap:
X-Region: US
X-Tenant: victim-corp
X-Region: U
X-Tenant: Svictim-corp
The above 2 examples would result in the same cache key, despite being different values. Changes to the cache key should be made to ensure values in this way don't collide.
This was previously reported to the Security Team by GeonHa. However, because it requires in depth knowledge of the system, a lack of user validation and similar values, it is not considered a vulnerability.
Change History
(13)
| Triage Stage: |
Unreviewed → Accepted
|
| Owner: |
set to gonas
|
| Status: |
new → assigned
|
| Owner: |
changed from gonas to Jacob Walls
|
| Patch needs improvement: |
set
|
| Patch needs improvement: |
unset
|
| Triage Stage: |
Accepted → Ready for checkin
|
| Resolution: |
→ fixed
|
| Status: |
assigned → closed
|
@Gonas Hey, are you still working on this? Happy to collaborate or take it over if you've moved on.