Spree API has Authenticated Insecure Direct Object Reference (IDOR) via Order Modification
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.2.5, 5.1.9, 5.0.7, 4.10.2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: poc
- Automatable: no
- Technical impact: partial
Summary
Spree is an open source e-commerce solution built with Ruby on Rails. Prior to versions 4.10.2, 5.0.7, 5.1.9, and 5.2.5, an Authenticated Insecure Direct Object Reference (IDOR) vulnerability was identified that allows an authenticated user to retrieve other users’ address information by modifying an existing order. By editing an order they legitimately own and manipulating address identifiers in the request, the backend server accepts and processes references to addresses belonging to other users, subsequently associating those addresses with the attacker’s order and returning them in the response. This issue has been patched in versions 4.10.2, 5.0.7, 5.1.9, and 5.2.5.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- spree spree
From 5.2.0 · fixed in 5.2.5; From 5.1.0 · fixed in 5.1.9; From 5.0.0 · fixed in 5.0.7; fixed in 4.10.2
- spree_apiRubyGems
From 3.7.0 · fixed in 4.10.2
- spree_apiRubyGems
From 5.0.0 · fixed in 5.0.7
- spree_apiRubyGems
From 5.1.0 · fixed in 5.1.9
- spree_apiRubyGems
From 5.2.0 · fixed in 5.2.5