Shopware's session is persistent in Cache for 404 pages
shopware
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| shopware/storefront Packagist |
|
|
| shopware/platform Packagist |
|
|
shopware
| Product | Affected | Fixed in |
|---|---|---|
| shopware/storefront Packagist |
|
|
| shopware/platform Packagist |
|
|
Shopware is an open commerce platform based on Symfony Framework and Vue. The Symfony Session Handler pops the Session Cookie and assigns it to the Response. Since Shopware 6.5.8.0, the 404 pages are cached to improve the performance of 404 pages. So the cached Response which contains a Session Cookie when the Browser accessing the 404 page, has no cookies yet. The Symfony Session Handler is in use, when no explicit Session configuration has been done. When Redis is in use for Sessions using the PHP Redis extension, this exploiting code is not used. Shopware version 6.5.8.7 contains a patch for this issue. As a workaround, use Redis for Sessions, as this does not trigger the exploit code.
From the CVE record · GitHub_M
In affected Shopware versions, a cached 404 response can contain a session cookie assigned by the Symfony Session Handler. A visitor accessing a 404 page without an existing cookie may receive that cached cookie when no explicit session configuration is set. This issue does not arise when sessions use Redis through the PHP Redis extension.
Operators running Packagist shopware/storefront or shopware/platform versions >=6.5.8.0 and <6.5.8.7 should check their installations.