Sensitive Information Exposure in Sylius

• ECOSYSTEM: introduced 0; fixed 1.9.10

### Impact Any other user can view the data if the browser tab remains open after logging out. Once someone logs out and leaves the browser open, the potential attacker may use the back button to see the content exposed on given screens. No action may be performed though, and any website refresh will block further reads. It may, however, lead to a data leak, like for example customer details, payment gateway configuration, etc.- but only if these were pages checked by the administrator. This vulnerability requires full access to the computer to take advantage of it. ### Patches The issue is fixed in versions: 1.9.10, 1.10.11, 1.11.2 and above. ### Workarounds The application must strictly redirect to the login page even when the browser back button is pressed. Another possibility is to set more strict cache policies for restricted content (like no-store). It can be achieved with the following class: ```php <?php declare(strict_types=1); namespace App\EventListener; use App\SectionResolver\ShopCustomerAccountSubSection; use Sylius\Bundle\AdminBundle\SectionResolver\AdminSection; use Sylius\Bundle\CoreBundle\SectionResolver\SectionProviderInterface; use Symfony\Component\Even

GitHub Advisory Database via OSV

• ECOSYSTEM: introduced 1.10; fixed 1.10.11

### Impact Any other user can view the data if the browser tab remains open after logging out. Once someone logs out and leaves the browser open, the potential attacker may use the back button to see the content exposed on given screens. No action may be performed though, and any website refresh will block further reads. It may, however, lead to a data leak, like for example customer details, payment gateway configuration, etc.- but only if these were pages checked by the administrator. This vulnerability requires full access to the computer to take advantage of it. ### Patches The issue is fixed in versions: 1.9.10, 1.10.11, 1.11.2 and above. ### Workarounds The application must strictly redirect to the login page even when the browser back button is pressed. Another possibility is to set more strict cache policies for restricted content (like no-store). It can be achieved with the following class: ```php <?php declare(strict_types=1); namespace App\EventListener; use App\SectionResolver\ShopCustomerAccountSubSection; use Sylius\Bundle\AdminBundle\SectionResolver\AdminSection; use Sylius\Bundle\CoreBundle\SectionResolver\SectionProviderInterface; use Symfony\Component\Even

GitHub Advisory Database via OSV

• ECOSYSTEM: introduced 1.11; fixed 1.11.2

### Impact Any other user can view the data if the browser tab remains open after logging out. Once someone logs out and leaves the browser open, the potential attacker may use the back button to see the content exposed on given screens. No action may be performed though, and any website refresh will block further reads. It may, however, lead to a data leak, like for example customer details, payment gateway configuration, etc.- but only if these were pages checked by the administrator. This vulnerability requires full access to the computer to take advantage of it. ### Patches The issue is fixed in versions: 1.9.10, 1.10.11, 1.11.2 and above. ### Workarounds The application must strictly redirect to the login page even when the browser back button is pressed. Another possibility is to set more strict cache policies for restricted content (like no-store). It can be achieved with the following class: ```php <?php declare(strict_types=1); namespace App\EventListener; use App\SectionResolver\ShopCustomerAccountSubSection; use Sylius\Bundle\AdminBundle\SectionResolver\AdminSection; use Sylius\Bundle\CoreBundle\SectionResolver\SectionProviderInterface; use Symfony\Component\Even

GitHub Advisory Database via OSV