Saleor vulnerabilities

In Saleor up to 3.20.118/3.21.54/3.22.47/3.23.14, the get_client_ip function in saleor/account/throttling.py allows bypassing authentication attempt throttling by spoofing the client IP. The vendor considers this intended behavior, stating that XFF should be configured properly. The exploit has been publicly disclosed.

Saleor from version 2.10.0rc1 to 3.21.67, 3.22.63, and 3.23.22 treats email verification as sufficient proof of account ownership and automatically associates anonymous commerce data with the newly activated account. An attacker can create an account with the victim's email address, and after the victim activates it, gain access to their order history and personal data.

Saleor versions from 3.14.67 to 3.21.67, 3.22.63, and 3.23.22 have a broken authorization check in saleor/permission/utils.py that can incorrectly authorize unauthenticated GraphQL requests. This allows anonymous callers to use the channelUpdate() mutation to change channel order settings such as allowUnpaidOrders even when the response reports PermissionDenied. The same permission utility can expose hidden objects through pageType() and translation() queries, including attributes with visibleInStorefront set to false.

Saleor, an e-commerce platform, from version 2.10.0 to before 3.23.0a3, 3.22.47, 3.21.54, and 3.20.118, has a vulnerability in the requestEmailChange() mutation that revealed the existence of user-provided email addresses in error messages. This is fixed in versions 3.23.0a3, 3.22.47, 3.21.54, and 3.20.118.

Saleor from 2.10.0 to before 3.23.0a3, 3.22.47, 3.21.54, and 3.20.118 has a business-logic and authorization flaw in the email change workflow. An email change token generated for one account can be replayed while authenticated as a different account, changing the second account's email to the token's new_email.

Saleor is an e-commerce platform. From 2.0.0 to before 3.23.0a3, 3.22.47, 3.21.54, and 3.20.118, a malicious actor can include many GraphQL mutations or queries in a single API call using aliases or chaining multiple mutations, resulting in resource exhaustion. This vulnerability is fixed in 3.23.0a3, 3.22.47, 3.21.54, and 3.20.118.

Saleor from version 2.0.0 to before 3.23.0a3, 3.22.47, 3.21.54, and 3.20.118 supports GraphQL query batching without limiting the number of operations. An unauthenticated attacker can send a single HTTP request with many operations, bypassing the per-query complexity limit.