Ability to expose data in Sylius by using an unintended serialisation group
SyliusResourceBundle
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| sylius/resource-bundle Packagist |
|
|
SyliusResourceBundle
| Product | Affected | Fixed in |
|---|---|---|
| sylius/resource-bundle Packagist |
|
|
| sylius/sylius Packagist |
|
|
Sylius ResourceBundle accepts and uses any serialisation groups to be passed via a HTTP header. This might lead to data exposure by using an unintended serialisation group - for example it could make Shop API use a more permissive group from Admin API. Anyone exposing an API with ResourceBundle's controller is affected. The vulnerable versions are: <1.3 || >=1.3.0 <=1.3.12 || >=1.4.0 <=1.4.5 || >=1.5.0 <=1.5.0 || >=1.6.0 <=1.6.2. The patch is provided for Sylius ResourceBundle 1.3.13, 1.4.6, 1.5.1 and 1.6.3, but not for any versions below 1.3.
From the CVE record · GitHub_M
SyliusResourceBundle accepts serialization groups supplied in an HTTP header. When an API uses its controller, a requester may select an unintended group and expose data, such as by applying a more permissive Admin API group to a Shop API response. Authentication requirements are not specified; no user interaction is described.
Teams exposing APIs through SyliusResourceBundle controllers should check affected sylius/resource-bundle and sylius/sylius versions, including ResourceBundle versions below 1.3, for which no patch is provided.