Spree does not properly restrict the use of a hash to provide values for a model's attributes
Spree 0.2.0 does not properly restrict the use of a hash to provide values for a model's attributes, which allows remote attackers to set the Order state value and bypass the intended payment step via a modified URL, related to a "mass assignment" vulnerability.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2008-7310US | medium5.0 | — | ||
Spree 0.2.0 does not properly restrict the use of a hash to provide values for a model's attributes, which allows remote attackers to set the Order state value and bypass the inten… | ||||
02
references
External citations — patches, advisories, analysis.
- http://railspikes.com/2008/9/22/is-your-rails-application-safe-from-mass-assignmentWEB
- http://spreecommerce.com/blog/2008/09/16/security-vulnerability-mass-assignment-of-order-paramsWEB
- https://github.com/rubysec/ruby-advisory-db/blob/master/gems/spree/CVE-2008-7310.ymlWEB
- https://github.com/spree/spreePACKAGE
- https://nvd.nist.gov/vuln/detail/CVE-2008-7310ADVISORY
- https://spreecommerce.com/blog/security-vulnerability-mass-assignmentWEB
- https://web.archive.org/web/20080925003904/http://railspikes.com/2008/9/22/is-your-rails-application-safe-from-mass-assignmentWEB
- https://web.archive.org/web/20101128024717/http://spreecommerce.com/blog/2008/09/16/security-vulnerability-mass-assignment-of-order-paramsWEB
scry
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