GHSA-3ghg-3787-w2xr Spree API has Unauthenticated IDOR - Guest Address

• RubyGems spree_core: >= 4.0.0, < 4.10.2 → fixed in 4.10.2 • RubyGems spree_core: >= 5.0.0, < 5.0.7 → fixed in 5.0.7 • RubyGems spree_core: >= 5.1.0, < 5.1.9 → fixed in 5.1.9 • RubyGems spree_core: >= 5.2.0, < 5.2.5 → fixed in 5.2.5

Summary An Unauthenticated Insecure Direct Object Reference (IDOR) vulnerability was identified that allows an unauthenticated attacker to access guest address information without supplying valid credentials or session cookies. Details During testing, it was observed that all guest users can make an unauthenticated request to retrieve address data belonging to other guest users by manipulating object identifiers. The attacker would need to know the storefront URL structure to perform this attack (which can be learnt after creating a registered user account). Affected Component(s) • Address Edit endpoint: `/addresses/{addressId}/edit` Root Cause • Faulty authorization check in CanCanCan Ability class: ```diff • can :manage, ::Spree::Address, user_id: user.id + can :manage, ::Spree::Address, user_id: user.id if user.persisted? ``` the `user` object in `Spree::Ability` class for guest users is a `Spree.user_class.new` object. Addresses endpoint to access it is part of the `spree_storefront` gem. Headless builds using APIs are not affected, as the Addresses endpoint there is only for registered users, and records are scoped to the currently signed-in user. PoC Preconditions • No authentication required • No cookies or session tokens set To reproduce this vulnerability simply perform the request shown below, replacing the number with an arbitrary value. For the initial request the Guest Address id = 6 is used to obtain the information Request GET `/addresses/6/edit` Repeat the request and check the response, in this example using Guest Address id = 2. Request GET `/addresses/2/edit` Impact An unauthenticated attacker can: • Enumerate and retrieve guest address information (Addresses associated with User accounts are NOT affected) • Access personally identifiable information (PII) such as: • Full names • Physical addresses • Phone numbers (if present) This vulnerability could lead to: • Privacy violations • Regulatory compliance issues (e.g., GDPR) • Loss of user trust