Disputed cache poisoning via parameter-insensitive caching
Published Mar 6, 2020 · Updated Aug 4, 2024
Cache poisoning in Citrix Gateway 11.1, 12.0, and 12.1 allows remote attackers to serve cached responses across parameter values. The reported caching path reuses the first response for later requests to the same URL even when submitted parameter values differ. A victim must request that URL during its cache lifetime; Citrix disputes any security impact because default caching covers only static-content paths.
Summary
What happened
Cache poisoning in Citrix Gateway 11.1, 12.0, and 12.1 allows remote attackers to serve cached responses across parameter values. The reported caching path reuses the first response for later requests to the same URL even when submitted parameter values differ. A victim must request that URL during its cache lifetime; Citrix disputes any security impact because default caching covers only static-content paths.
The record
- CVE
- CVE-2020-10112
- Published
- Mar 6, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-444, CAPEC-141
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 6, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Citrix Gateway cache-poisoning proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo