sylius/sylius
Affected
- introduced
1.9.0, fixed1.9.5(ecosystem)
Fixed versions
1.9.5
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: CVE-2021-32720
List of order ids, number, items total and token value exposed for unauthorized uses via new API
Impact
Part of the details (order ID, order number, items total, and token value) of all placed orders were exposed to unauthorized users. If exploited properly, a few additional information like the number of items in the cart and the date of the shipping may be fetched as well. This data seems to not be crucial nor is personal data, however, could be used for sociotechnical attacks or may expose a few details about shop condition to the third parties. The data possible to aggregate are the number of processed orders or their value in the moment of time.
Patches
The problem has been patched at Sylius 1.9.5 and 1.10.0
Workarounds
There are a few ways to fix this without updating the code.
The first possible solution is to hide the problematic endpoints behind the firewall from not logged in users. In order to achieve it one has to add the configuration in config/packages/security.yaml:
access_control:
# ...
- { path: "%sylius.security.new_api_shop_regex%/orders", role: IS_AUTHENTICATED_ANONYMOUSLY, methods: [POST] }
- { path: "%sylius.security.new_api_shop_regex%/orders", role: ROLE_USER, methods: [GET] }
This would put only the order list under the firewall and allow only authorized users to access it. Once a user is authorized, it will have access to theirs orders only.
The second possible solution is to decorate the \Sylius\Bundle\ApiBundle\Doctrine\QueryCollectionExtension\OrdersByLoggedInUserExtension and throw Symfony\Component\Security\Core\Exception\AccessDeniedException if the class is executed for unauthorized user.
Medium Basis: The source's own band: MODERATE
1.9.0, fixed 1.9.5 (ecosystem)1.9.5
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0