Cross-Site Request Forgery (CSRF) in solidus_frontend (CVE-2021-43846)
Summary
Vulnerability in solidus_frontend (CVE-2021-43846). Risk of unauthorized operations or information disclosure. Exploitable via solidus_frontend. Mitigation: upgrade to 3.1.5 or later.
Original description
The description as published by the source.
solidus_frontend is the cart and storefront for the Solidus e-commerce project. Versions of solidus_frontend prior to 3.1.5, 3.0.5, and 2.11.14 contain a cross-site request forgery (CSRF) vulnerability that allows a malicious site to add an item to the user's cart without their knowledge. Versions 3.1.5, 3.0.5, and 2.11.14 contain a patch for this issue. The patch adds CSRF token verification to the "Add to cart" action. Adding forgery protection to a form that missed it can have some side effects. Other CSRF protection strategies as well as a workaround involving modifcation to config/application.rb` are available. More details on these mitigations are available in the GitHub Security Advisory.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2021-43846 has been found in solidus_frontend.
Attackers can target a specific entry point like solidus_frontend over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade solidus_frontend to 3.1.5 or later.
If unsure, ask your IT team or search "solidus_frontend CVE-2021-43846" on the vendor's site.
CVE-2021-43846 (solidus_frontend) — CWE-352
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: solidus_frontend
Patched: 3.1.5 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
CSRF (CWE-352) exists in solidus_frontend. Attackers reach the vulnerable code path via solidus_frontend without authentication.
Check the vendor advisory for the affected versions of solidus_frontend. Attack surface: solidus_frontend.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 3.1.5.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'solidus_frontend' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'solidus_frontend' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
solidus_frontendを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade solidus_frontend to 3.1.5ステージング環境で 3.1.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- patch github.com
- patch github.com
- report github.com
- web github.com