NetSight
high7.4

CVE-2020-15269

Ensure that doorkeeper_token is valid when authenticating requests in API v2 calls

Impact

### Impact The perpetrator who previously obtained an old expired user token could use it to access Storefront API v2 endpoints. ### Patches Please upgrade to 3.7.11, 4.0.4, or 4.1.11 depending on your used Spree version. ### Workarounds In your project directory create a decorator file `app/controllers/spree/api/v2/base_controller_decotatror.rb` with contents: ```ruby module Spree module Api module V2 module BaseControllerDecorator private def spree_current_user return nil unless doorkeeper_token return @spree_current_user if @spree_current_user doorkeeper_authorize! @spree_current_user ||= ::Spree.user_class.find_by(id: doorkeeper_token.resource_owner_id) end end end end Spree::Api::V2::BaseController.prepend(Spree::Api::V2::BaseControllerDecorator) ``` ### For more information If you have any questions or comments about this advisory: * Email us at [security@spreecommerce.org](mailto:security@spreecommerce.org)

Affected packages

EcosystemPackageAffectedFixed in
rubygemsspree< 3.7.113.7.11

Affected products

VendorProductAffected versions
SparksolutionsSpree
before 3.7.11
from 4.0.0 before 4.0.4
from 4.1.0 before 4.1.11

Weakness classification

References