http-cache-semantics through 4.2.0 fails to properly validate security-zeroed cache entries when processing client max-stale directives, allowing unauthenticated attackers to retrieve cached responses belonging to other users. Attackers can request the same URL with a large max-stale value to obtain another user's Set-Cookie session credentials from shared-cache entries that were deliberately zeroed for security reasons.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
Low
Easy to exploit
Attack Requirements
None
No additional conditions
Privileges Required
None
No privileges needed
User Interaction
None
No user interaction needed
Impact Assessment
Confidentiality
High
Complete data leak
Integrity
None
No data modification
Availability
None
No disruption
CVSS Vector v4.0
Weakness Type (CWE)
References 5
https://github.com/kornelski/http-cache-semantics
disclosure@vulncheck.com
https://github.com/kornelski/http-cache-semantics/blob/f01112e954b83cfa8765b633…
disclosure@vulncheck.com
https://github.com/kornelski/http-cache-semantics/blob/f01112e954b83cfa8765b633…
disclosure@vulncheck.com
https://github.com/kornelski/http-cache-semantics/issues/56
disclosure@vulncheck.com
https://www.vulncheck.com/advisories/http-cache-semantics-through-4.2.0-cross-u…
disclosure@vulncheck.com