{"answers":{"affected":"6 open source packages ship an affected version, including solidus_core.","exploited":"There is no known exploitation of GHSA-5629-8855-gf4g in the wild and no public exploit code.","fix":"Upgrade solidus_core to a fixed version for your release line: 2.11.12, 3.0.3 or 3.1.3.","what":"GHSA-5629-8855-gf4g is a vulnerability in solidus_core, published on 18 Nov 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for GHSA-5629-8855-gf4g and fix it if it is affected.\n\nWhat it is: GHSA-5629-8855-gf4g is a vulnerability in solidus_core, published on 18 Nov 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of GHSA-5629-8855-gf4g in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- solidus_core (RubyGems): affected all versions; fixed in 2.11.12\n- solidus_core (RubyGems): affected all versions; fixed in 2.11.12\n- solidus_core (RubyGems): affected from 3.0.0; fixed in 3.0.3\n- solidus_core (RubyGems): affected from 3.0.0; fixed in 3.0.3\n- solidus_core (RubyGems): affected from 3.1.0; fixed in 3.1.3\n- solidus_core (RubyGems): affected from 3.1.0; fixed in 3.1.3\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/GHSA-5629-8855-gf4g/ (Markdown: https://insights.sbomify.com/GHSA-5629-8855-gf4g/index.md)","id":"GHSA-5629-8855-gf4g","markdown":"https://insights.sbomify.com/GHSA-5629-8855-gf4g/index.md","name":"GHSA-5629-8855-gf4g","record":{"aliases":[],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Solidus e-commerce","requires_auth":"none","summary":"Attackers can bypass authentication via CSRF to take over user accounts in Solidus e-commerce applications.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"### Impact\nThe actual vulnerability has been discovered on `solidus_auth_devise`. See [GHSA-xm34-v85h-9pg2](https://github.com/solidusio/solidus_auth_devise/security/advisories/GHSA-xm34-v85h-9pg2) for details.\n\nThe security advisory here exists to provide an extra layer of security in the form of a monkey patch for users who don't update `solidus_auth_devise`. For this reason, it has been marked as low impact on this end.\n\n### Patches\nFor extra security, update `solidus_core` to versions `3.1.3`, `3.0.3` or `2.11.12`.\n\n### Workarounds\nLook at the workarounds described at [GHSA-xm34-v85h-9pg2](https://github.com/solidusio/solidus_auth_devise/security/advisories/GHSA-xm34-v85h-9pg2).\n\n### References\n- [GHSA-xm34-v85h-9pg2](https://github.com/solidusio/solidus_auth_devise/security/advisories/GHSA-xm34-v85h-9pg2).\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [solidus_auth_devise](https://github.com/solidusio/solidus_auth_devise/issues) or a discussion in [solidus](https://github.com/solidusio/solidus/discussions)\n* Email us at [security@solidus.io](mailto:security@soliidus.io)\n* Contact the core team on [Slack](http://slack.solidus.io/)","ecosystems":["RubyGems"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Authentication Bypass by CSRF Weakness","id":"GHSA-5629-8855-gf4g","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"RubyGems","product":null,"products":[],"type":"csrf","year":"2021"},"n_packages":6,"n_references":null,"packages":[{"ecosystem":"RubyGems","fixed":["2.11.12"],"introduced":["0"],"last_affected":[],"package":"solidus_core","purl":null,"source":"GHSA-5629-8855-gf4g"},{"ecosystem":"RubyGems","fixed":["2.11.12"],"introduced":["0"],"last_affected":[],"package":"solidus_core","purl":"pkg:gem/solidus_core","source":"GHSA-5629-8855-gf4g"},{"ecosystem":"RubyGems","fixed":["3.0.3"],"introduced":["3.0.0"],"last_affected":[],"package":"solidus_core","purl":null,"source":"GHSA-5629-8855-gf4g"},{"ecosystem":"RubyGems","fixed":["3.0.3"],"introduced":["3.0.0"],"last_affected":[],"package":"solidus_core","purl":"pkg:gem/solidus_core","source":"GHSA-5629-8855-gf4g"},{"ecosystem":"RubyGems","fixed":["3.1.3"],"introduced":["3.1.0"],"last_affected":[],"package":"solidus_core","purl":null,"source":"GHSA-5629-8855-gf4g"},{"ecosystem":"RubyGems","fixed":["3.1.3"],"introduced":["3.1.0"],"last_affected":[],"package":"solidus_core","purl":"pkg:gem/solidus_core","source":"GHSA-5629-8855-gf4g"}],"products":null,"published":"2021-11-18","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Attackers can bypass authentication via CSRF to take over user accounts in Solidus e-commerce applications.","url":"https://insights.sbomify.com/GHSA-5629-8855-gf4g/"}