HTTP caching is marking private HTTP headers as public
shopware platform
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| shopware/platform Packagist |
|
|
| shopware/core Packagist |
|
|
| shopware/storefront Packagist |
shopware platform
| Product | Affected | Fixed in |
|---|---|---|
| shopware/platform Packagist |
|
|
| shopware/core Packagist |
|
|
| shopware/storefront Packagist |
< 6.4.8.2
|
Shopware is an open commerce platform based on the Symfony php Framework and the Vue javascript framework. Affected versions of shopware do no properly set sensitive HTTP headers to be non-cacheable. If there is an HTTP cache between the server and client then headers may be exposed via HTTP caches. This issue has been resolved in version 6.4.8.2. There are no known workarounds.
From the CVE record · GitHub_M
Affected Shopware versions do not properly mark sensitive HTTP headers as non-cacheable. If an HTTP cache sits between the server and client, those headers may be exposed through the cache; the input does not specify whether authentication or user interaction is needed.
Engineers running shopware/platform, shopware/core, or shopware/storefront versions earlier than 6.4.8.2 should check their installations.