← Back
GHSA-j8v8-g9cx-5qf4
Vulnerability in @better-auth/scim (GHSA-j8v8-g9cx-5qf4)
Summary
vulnerability in @better-auth/scim (GHSA-j8v8-g9cx-5qf4). Risk of unauthorized operations or information disclosure. Exploitable via `POST /scim/generate-token`. Mitigation: upgrade to `1.7.0-beta.4` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **GHSA-j8v8-g9cx-5qf4** has been found in @better-auth/scim.
Attackers can target a specific entry point like `POST /scim/generate-token` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade @better-auth/scim to **1.7.0-beta.4** or later.
If unsure, ask your IT team or search "@better-auth/scim GHSA-j8v8-g9cx-5qf4" on the vendor's site.
GHSA-j8v8-g9cx-5qf4 (@better-auth/scim) — CWE-639 /
Attack surface: POST /scim/generate-token / GET /scim/get-provider-connection / GET /scim/v2/Users / `organizationId`
Patched: `1.7.0-beta.4` — 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/scim. Attackers reach the vulnerable code path via `POST /scim/generate-token` without authentication.
📍 Affected scope
@better-auth/scim — . Attack surface: POST /scim/generate-token / GET /scim/get-provider-connection / GET /scim/v2/Users / `organizationId`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1.7.0-beta.4**.
🛡️ 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 `POST /scim/generate-token` requests with malformed payloads or SQL meta-characters. Run `grep -r '@better-auth/scim' .` 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/scim' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `@better-auth/scim` を grep し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'POST /scim/generate-token' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `POST /scim/generate-token` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
6Apply patch patch
Upgrade @better-auth/scim to 1.7.0-beta.4ステージング環境で 1.7.0-beta.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Replay attack against POST /scim/generate-token on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
@better-auth/scim
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.7.0-beta.4"}]}]