CVE-2020-15269GHSA-F8CM-364F-Q9QH
Expired token reuse in Spree
- 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 3.7.11, 4.0.4, 4.1.11
- 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
Summary
In Spree before versions 3.7.11, 4.0.4, or 4.1.11, expired user tokens could be used to access Storefront API v2 endpoints. The issue is patched in versions 3.7.11, 4.0.4 and 4.1.11. A workaround without upgrading is described in the linked advisory.
Timeline
- CVE published
- Record last updated
Affected versions
- spree spree
fixed in 3.7.11; From 4.0.0 · fixed in 4.0.4; From 4.1.0 · fixed in 4.1.11
- spreeRubyGems
fixed in 3.7.11
- spreeRubyGems
From 4.0.0 · fixed in 4.0.4
- spreeRubyGems
From 4.1.0 · fixed in 4.1.11