CVE-2008-7311
Spree Hardcoded config.action_controller_session Hash Value Cryptographic Protection Weakness
Overview
Description
The session cookie store implementation in Spree 0.2.0 uses a hardcoded config.action_controller_session hash value (aka secret key), which makes it easier for remote attackers to bypass cryptographic protection mechanisms by leveraging an application that contains this value within the config/environment.rb file.
Source: OX vulnerability database
Severity
5 · MEDIUM
CVSS 2.0 base score, scored by NVD.
- Access vector
- Network
- Access complexity
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:N/I:P/A:N
Weakness: CWE-255
Affected packages · 1
| Ecosystem | Package | Vulnerable | Fixed in |
|---|---|---|---|
| RubyGems | spree | <0.4.0 | 0.4.00.3.0 |
Open a package to see all its vulnerabilities.
Operating systems
No Linux distribution reports this ID.
References
- spreecommerce.com http://spreecommerce.com/blog/2008/08/12/security-vulernability-session-cookie-store
- spreecommerce.com http://spreecommerce.com/blog/2008/08/12/security-vulernability-session-cookie-store/
- support.spreehq.org http://support.spreehq.org/issues/show/63
- github.com https://github.com/rubysec/ruby-advisory-db/blob/master/gems/spree/CVE-2008-7311.yml
- github.com https://github.com/spree/spree
- nvd.nist.gov https://nvd.nist.gov/vuln/detail/CVE-2008-7311
- spreecommerce.com https://spreecommerce.com/blog/security-vulernability-session-cookie-store
- web.archive.org https://web.archive.org/web/20090306033106/http://support.spreehq.org/issues/show/63
- web.archive.org https://web.archive.org/web/20100309050152/http://rubygems.org/gems/spree/versions
- web.archive.org https://web.archive.org/web/20101128024939/http://spreecommerce.com/blog/2008/08/12/security-vulernability-session-cookie-store
OX Radar and Response Center
Find threats in your stack.
OX Radar can check high-priority threats, like critical package CVEs, against your context.
Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.