Authorization bypass in Spree
### Impact The perpetrator could query the [API v2 Order Status](https://guides.spreecommerce.org/api/v2/storefront#tag/Order-Status) endpoint with an empty string passed as an Order token ### Patches Please upgrade to 3.7.11, 4.0.4, or 4.1.11 depending on your used Spree version. Users of Spree < 3.7 are not affected. ### References Pull request with a fix and in-depth explanation - https://github.com/spree/spree/pull/10573 ### For more information If you have any questions or comments about this advisory: * Email us at [security@spreecommerce.org](mailto:security@spreecommerce.org)
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2020-26223US | medium6.5OT elevated | — | ||
Spree is a complete open source e-commerce solution built with Ruby on Rails. In Spree from version 3.7 and before versions 3.7.13, 4.0.5, and 4.1.12, there is an authorization byp… | ||||
references
External citations — patches, advisories, analysis.
- https://github.com/rubysec/ruby-advisory-db/blob/master/gems/spree_api/CVE-2020-26223.ymlWEB
- https://github.com/spree/spreePACKAGE
- https://github.com/spree/spree/pull/10573WEB
- https://github.com/spree/spree/security/advisories/GHSA-m2jr-hmc3-qmprWEB
- https://guides.spreecommerce.org/api/v2/storefront#tag/Order-StatusWEB
- https://nvd.nist.gov/vuln/detail/CVE-2020-26223ADVISORY
- https://rubygems.org/gems/spree_api/versionsWEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan