Shopware vulnerable to Improper Access Control with ManyToMany associations in store-api
shopware
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| shopware/core Packagist |
|
|
| shopware/platform Packagist |
|
shopware
| Product | Affected | Fixed in |
|---|---|---|
| shopware/core Packagist |
|
|
| shopware/platform Packagist |
|
|
Shopware is an open commerce platform. The store-API works with regular entities and not expose all fields for the public API; fields need to be marked as ApiAware in the EntityDefinition. So only ApiAware fields of the EntityDefinition will be encoded to the final JSON. Prior to versions 6.6.5.1 and 6.5.8.13, the processing of the Criteria did not considered ManyToMany associations and so they were not considered properly and the protections didn't get used. This issue cannot be reproduced with the default entities by Shopware, but can be triggered with extensions. Update to Shopware 6.6.5.1 or 6.5.8.13 to receive a patch. For older versions of 6.2, 6.3, and 6.4, corresponding security measures are also available via a plugin.
From the CVE record · GitHub_M
Shopware’s Store API does not properly apply field protections when processing ManyToMany associations in Criteria. Extensions can trigger this issue, potentially exposing fields not marked for the public API; it cannot be reproduced with Shopware’s default entities. The input does not specify whether authentication or user interaction is required.
Operators using Packagist shopware/core or shopware/platform versions below 6.5.8.13, or versions from 6.6.0.0 up to but not including 6.6.5.1, should check their installations.