← Back
GHSA-xf4v-w5x5-pv79
Vulnerability in spree (GHSA-xf4v-w5x5-pv79)
Summary
vulnerability in spree (GHSA-xf4v-w5x5-pv79). Risk of unauthorized operations or information disclosure. Exploitable via ``CustomerPresenter``. Mitigation: upgrade to `5.4.3` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **GHSA-xf4v-w5x5-pv79** has been found in spree.
Attackers can target a specific entry point like ``CustomerPresenter`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade spree to **5.4.3** or later.
If unsure, ask your IT team or search "spree GHSA-xf4v-w5x5-pv79" on the vendor's site.
GHSA-xf4v-w5x5-pv79 (spree) — CWE-1236 /
Attack surface: `CustomerPresenter` / `first_name` / `last_name` / `address1`
Patched: `5.4.3` — 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.
❓ What is the problem
**A vulnerability** (CWE-1236) exists in spree. Attackers reach the vulnerable code path via ``CustomerPresenter`` without authentication.
📍 Affected scope
spree — . Attack surface: `CustomerPresenter` / `first_name` / `last_name` / `address1`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **5.4.3**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'spree' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'spree' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `spree` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade spree to 5.4.3ステージング環境で 5.4.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
rubygems
spree
[{"type":"ECOSYSTEM","events":[{"introduced":"5.4.0"},{"fixed":"5.4.3"}]}]
References
- package https://github.com/spree/spree
- web https://github.com/spree/spree/security/advisories/GHSA-xf4v-w5x5-pv79
- web https://github.com/spree/spree/releases/tag/v5.2.8
- web https://github.com/spree/spree/releases/tag/v5.3.6
- web https://github.com/spree/spree/releases/tag/v5.4.3
- web https://github.com/advisories/GHSA-xf4v-w5x5-pv79