CVE-2010-3978: Exposure of Sensitive Information to an Unauthorized Actor
(updated )
Spree exchanges data using JavaScript Object Notation (JSON) without a mechanism for validating requests, which allows remote attackers to obtain sensitive information via vectors involving (1) admin/products.json, (2) admin/users.json, or (3) admin/overview/get_report_data, related to a “JSON hijacking” issue.
References
- spreecommerce.com/blog/2010/11/02/json-hijacking-vulnerability/
- spreecommerce.com/blog/2010/11/09/spree-0-30-0-released/
- twitter.com/conviso/statuses/29555076248
- www.conviso.com.br/json-hijacking-vulnerability/
- www.conviso.com.br/security-advisory-spree-e-commerce-json-v-0-11x/
- www.securityfocus.com/archive/1/514674/100/0/threaded
- github.com/railsdog/spree/commit/19944bd999c310d9b10d16a41f48ebac97dc4fac
- github.com/railsdog/spree/commit/d881b2bb610ea33e2364ff16feb8e702dfeda135
- nvd.nist.gov/vuln/detail/CVE-2010-3978
Code Behaviors & Features
Detect and mitigate CVE-2010-3978 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Dependency Scanning using SBOM also detects vulnerabilities from proprietary advisories that this site does not include. Learn more about Dependency Scanning using SBOM →