CVE-2019-19326GHSA-Q9FF-3Q93-FM8M
Silverstripe CMS sites through 4.4.4 which have opted into HTTP Cache Headers on responses served by the framework's HTTP layer can be vulne
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 4.4.7, 4.5.4, 3.7.5
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Silverstripe CMS sites through 4.4.4 which have opted into HTTP Cache Headers on responses served by the framework's HTTP layer can be vulnerable to web cache poisoning. Through modifying the X-Original-Url and X-HTTP-Method-Override headers, responses with malicious HTTP headers can return unexpected responses to other consumers of this cached response. Most other headers associated with web cache poisoning are already disabled through request hostname forgery whitelists.
Timeline
- CVE published
- Record last updated
Affected versions
- n/a n/a
Version range not reported
- silverstripe/frameworkPackagist
From 4.0.0 · fixed in 4.4.7
- silverstripe/frameworkPackagist
From 4.5.0 · fixed in 4.5.4
- silverstripe/frameworkPackagist
From 3.0.0 · fixed in 3.7.5