Headline

GHSA-c2f9-4jmm-v45m: Shopware's session is persistent in Cache for 404 pages

Impact

The Symfony Session Handler, pop’s the Session Cookie and assign 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, 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.

Patches

Update to Shopware version 6.5.8.7

Workarounds

Using Redis for Sessions, as this does not trigger the exploit code. Example configuration for Redis

# php.ini
session.save_handler = redis
session.save_path = "tcp://127.0.0.1:6379"

Consequences

As an guest browser session has been cached on a 404 page, every missing image or directly reaching a 404 page will logout the customer or clear his cart.

8 months ago

ghsa

Open in Source

#redis #git #php

Impact

The Symfony Session Handler, pop’s the Session Cookie and assign 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, 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.

Patches

Update to Shopware version 6.5.8.7

Workarounds

Using Redis for Sessions, as this does not trigger the exploit code. Example configuration for Redis

php.ini

session.save_handler = redis session.save_path = “tcp://127.0.0.1:6379”

Consequences

As an guest browser session has been cached on a 404 page, every missing image or directly reaching a 404 page will logout the customer or clear his cart.

References