← Back
GHSA-97pr-9hgg-3p8r

Information Disclosure in parse-server (GHSA-97pr-9hgg-3p8r)

Summary

vulnerability in parse-server (GHSA-97pr-9hgg-3p8r). Risk of unauthorized operations or information disclosure. Exploitable via ``save``. Mitigation: upgrade to `8.6.83` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **GHSA-97pr-9hgg-3p8r** has been found in parse-server. Attackers can target a specific entry point like ``save`` over the network to misuse the product. Risk of unauthorized operations or information disclosure. CVSS score: ?/10. What to do: upgrade parse-server to **8.6.83** or later. If unsure, ask your IT team or search "parse-server GHSA-97pr-9hgg-3p8r" on the vendor's site.
GHSA-97pr-9hgg-3p8r (parse-server) — CWE-200 / Attack surface: `save` / `leave` / `enter` Patched: `8.6.83` — apply immediately Workaround: Do not change an object's field values and a subscriber's ACL read access in the same `save` on LiveQuery-enabled classes; perform the access-control change in a separate save before or after the content change. 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
**information disclosure** (CWE-200) exists in parse-server. Attackers reach the vulnerable code path via ``save`` without authentication.
📍 Affected scope
parse-server — . Attack surface: `save` / `leave` / `enter`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **8.6.83**.
🛡️ Workaround
Workaround: Do not change an object's field values and a subscriber's ACL read access in the same `save` on LiveQuery-enabled classes; perform the access-control change in a separate save before or after the content change.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'parse-server' .` 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

  1. 1
    Identify exposure identify
    grep -r 'parse-server' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `parse-server` を grep し、稼働しているサービス・バージョンを把握する。

  2. 5
    Apply temporary workaround mitigate
    Do not change an object's field values and a subscriber's ACL read access in the same `save` on LiveQuery-enabled classes; perform the access-control change in a separate save before or after the content change.

    パッチが適用されるまでの応急処置として、Do not change an object's field values and a subscriber's ACL read access in the same `save` on LiveQuery-enabled classes; perform the access-control change in a separate save before or after the content change. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 6
    Apply patch patch
    Upgrade parse-server to 8.6.83

    ステージング環境で 8.6.83 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

  4. 7
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

npm parse-server
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.6.83"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →