{"answers":{"affected":"2 open source packages ship an affected version, including spree. It affects 1 product.","exploited":"There is no known exploitation of CVE-2008-7311 in the wild and no public exploit code.","fix":"Upgrade spree to 0.4.0 or later.","what":"CVE-2008-7311 is a medium-severity vulnerability in n/a, published on 4 Apr 2012. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2008-7311 and fix it if it is affected.\n\nWhat it is: CVE-2008-7311 is a medium-severity vulnerability in n/a, published on 4 Apr 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2008-7311 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- spree (RubyGems): affected all versions; fixed in 0.4.0\n- spree (RubyGems): affected all versions; fixed in 0.4.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2008-7311/ (Markdown: https://insights.sbomify.com/CVE-2008-7311/index.md)","id":"CVE-2008-7311","markdown":"https://insights.sbomify.com/CVE-2008-7311/index.md","name":"CVE-2008-7311","record":{"aliases":["GHSA-g466-57gh-cqfw"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Spree e-commerce platform","requires_auth":"none","summary":"Remote attackers can bypass session security in Spree by exploiting a hardcoded secret key, allowing them to forge valid session cookies.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"spree","vendor":"spreecommerce"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:N/I:P/A:N","version":"2.0"},"cwes":[{"id":"CWE-255","name":null}],"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.","ecosystems":["RubyGems"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Spree uses a hardcoded hash value","id":"CVE-2008-7311","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"RubyGems","product":null,"products":[],"type":"hardcoded_credentials","year":"2008"},"n_packages":2,"n_references":2,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2008-7312"},"packages":[{"ecosystem":"RubyGems","fixed":["0.4.0"],"introduced":["0"],"last_affected":[],"package":"spree","purl":null,"source":"GHSA-g466-57gh-cqfw"},{"ecosystem":"RubyGems","fixed":["0.4.0"],"introduced":["0"],"last_affected":[],"package":"spree","purl":"pkg:gem/spree","source":"GHSA-g466-57gh-cqfw"}],"prev":{"headline":"Spree does not properly restrict the use of a hash to provide values for a model's attributes","id":"CVE-2008-7310"},"products":["n/a"],"published":"2012-04-04","related":[{"cvss_score":10,"headline":"Spreecommerce \u003c 0.60.2 Search Parameter RCE","id":"CVE-2011-10019","kev_date_added":null,"published":"2025-08-13"},{"cvss_score":9.3,"headline":"Spreecommerce \u003c 0.50.x API RCE","id":"CVE-2011-10026","kev_date_added":null,"published":"2025-08-20"},{"cvss_score":7.7,"headline":"Unauthenticated Spree Commerce users can view completed guest orders by Order ID","id":"CVE-2026-25757","kev_date_added":null,"published":"2026-02-06"},{"cvss_score":7.7,"headline":"Spree allows unauthenticated users can access all guest addresses","id":"CVE-2026-25758","kev_date_added":null,"published":"2026-02-06"},{"cvss_score":7.7,"headline":"Authorization bypass in Spree","id":"CVE-2020-26223","kev_date_added":null,"published":"2020-11-13"},{"cvss_score":7.5,"headline":"Spree API has Unauthenticated IDOR - Guest Address","id":"CVE-2026-22589","kev_date_added":null,"published":"2026-01-10"},{"cvss_score":6.5,"headline":"Spree API has Authenticated Insecure Direct Object Reference (IDOR) via Order Modification","id":"CVE-2026-22588","kev_date_added":null,"published":"2026-01-08"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-17","vendors":["n/a"]},"summary":"Remote attackers can bypass session security in Spree by exploiting a hardcoded secret key, allowing them to forge valid session cookies.","url":"https://insights.sbomify.com/CVE-2008-7311/"}