# GHSA-5629-8855-gf4g: Authentication Bypass by CSRF Weakness

> Attackers can bypass authentication via CSRF to take over user accounts in Solidus e-commerce applications.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 18 Nov 2021

## What is GHSA-5629-8855-gf4g?

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.

### Official description

### Impact
The 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.

The 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.

### Patches
For extra security, update `solidus_core` to versions `3.1.3`, `3.0.3` or `2.11.12`.

### Workarounds
Look at the workarounds described at [GHSA-xm34-v85h-9pg2](https://github.com/solidusio/solidus_auth_devise/security/advisories/GHSA-xm34-v85h-9pg2).

### References
- [GHSA-xm34-v85h-9pg2](https://github.com/solidusio/solidus_auth_devise/security/advisories/GHSA-xm34-v85h-9pg2).

### For more information
If you have any questions or comments about this advisory:
* 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)
* Email us at [security@solidus.io](mailto:security@soliidus.io)
* Contact the core team on [Slack](http://slack.solidus.io/)

## Which versions are affected by GHSA-5629-8855-gf4g?

6 open source packages ship an affected version, including solidus_core.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `solidus_core` | RubyGems | All versions | 2.11.12 |
| `solidus_core` | RubyGems | All versions | 2.11.12 |
| `solidus_core` | RubyGems | From 3.0.0 | 3.0.3 |
| `solidus_core` | RubyGems | From 3.0.0 | 3.0.3 |
| `solidus_core` | RubyGems | From 3.1.0 | 3.1.3 |
| `solidus_core` | RubyGems | From 3.1.0 | 3.1.3 |

## How do I fix GHSA-5629-8855-gf4g?

Upgrade solidus_core to a fixed version for your release line: 2.11.12, 3.0.3 or 3.1.3.

## Is GHSA-5629-8855-gf4g being exploited?

There is no known exploitation of GHSA-5629-8855-gf4g in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-5629-8855-gf4g and fix it if it is affected.

What 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.
Exploitation: There is no known exploitation of GHSA-5629-8855-gf4g in the wild and no public exploit code.

Affected packages and fixed versions:
- solidus_core (RubyGems): affected all versions; fixed in 2.11.12
- solidus_core (RubyGems): affected all versions; fixed in 2.11.12
- solidus_core (RubyGems): affected from 3.0.0; fixed in 3.0.3
- solidus_core (RubyGems): affected from 3.0.0; fixed in 3.0.3
- solidus_core (RubyGems): affected from 3.1.0; fixed in 3.1.3
- solidus_core (RubyGems): affected from 3.1.0; fixed in 3.1.3

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-5629-8855-gf4g/ (Markdown: https://insights.sbomify.com/GHSA-5629-8855-gf4g/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-5629-8855-gf4g

---
From sbomify Insights: https://insights.sbomify.com/GHSA-5629-8855-gf4g/
Summaries are generated and may contain mistakes; the official description above is the record.