Add OWASP cache key evidence fixtures#2117
Open
DENGXUELIN wants to merge 1 commit into
Open
Conversation
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
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.
/claim #1733
Summary
Adds fixture-backed web cache poisoning and cache-key evidence handling to
owasp-top-10-web.Changes include:
CACHE-KEY-01throughCACHE-KEY-08for cache boundary inventory, cache key inputs, origin input inventory, unkeyed influence, cacheability evidence, user/tenant separation, normalization parity, and poison impactVary/cache-key handling versus path-only cache keys withX-Forwarded-Hostinfluence on canonical and script URLsWhy
The existing #1734, #1735, and #1874 PRs add useful
SKILL.mdguidance, but they do not add local regression fixtures. This PR keeps the change focused and adds concrete benign and vulnerable examples so future reviews distinguish cacheability evidence from cache-key safety.Validation
git diff --check origin/main...HEADCACHE-KEY-01throughCACHE-KEY-08,Web Cache Poisoning / Cache-Key Evidence Gate,Cache Key Inputs,Unkeyed Influence,X-Forwarded-Host,Cache-Control,PortSwigger Web Cache Poisoning,Treating cacheability headers as cache-key proof, andversion: "1.0.2"Cache-Control,X-CDN-Cache-Key,Accept-Language,Vary, keyed host/query/locale policy, ignoredX-Forwarded-Host, andreq.originalUrlgit merge-tree --write-tree origin/main HEADBounty
I have read and agree to the CONTRIBUTING.md bounty terms. Requested Improver Moderate tier if accepted.