← Back
GHSA-h3rm-78g3-j7cp
Vulnerability in @better-auth/stripe (GHSA-h3rm-78g3-j7cp)
Summary
vulnerability in @better-auth/stripe (GHSA-h3rm-78g3-j7cp). Risk of unauthorized operations or information disclosure. Exploitable via ``authorizeReference``. Mitigation: upgrade to `1.7.0-beta.10` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **GHSA-h3rm-78g3-j7cp** has been found in @better-auth/stripe.
Attackers can target a specific entry point like ``authorizeReference`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade @better-auth/stripe to **1.7.0-beta.10** or later.
If unsure, ask your IT team or search "@better-auth/stripe GHSA-h3rm-78g3-j7cp" on the vendor's site.
GHSA-h3rm-78g3-j7cp (@better-auth/stripe) — CWE-639 /
Attack surface: `authorizeReference` / `false`
Patched: `1.7.0-beta.10` — 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-639) exists in @better-auth/stripe. Attackers reach the vulnerable code path via ``authorizeReference`` without authentication.
📍 Affected scope
@better-auth/stripe — . Attack surface: `authorizeReference` / `false`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1.7.0-beta.10**.
🛡️ 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 '@better-auth/stripe' .` 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 '@better-auth/stripe' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `@better-auth/stripe` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade @better-auth/stripe to 1.7.0-beta.10ステージング環境で 1.7.0-beta.10 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
@better-auth/stripe
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.7.0-beta.10"}]}]
References
- web https://github.com/better-auth/better-auth/security/advisories/GHSA-h3rm-78g3-j7cp
- web https://github.com/better-auth/better-auth/commit/29fbcb573261242d8a05b131a9d39c9ae4352b06
- web https://github.com/better-auth/better-auth/releases/tag/v1.6.21
- web https://github.com/better-auth/better-auth/releases/tag/v1.7.0-beta.10
- web https://github.com/advisories/GHSA-h3rm-78g3-j7cp