Information Disclosure in parse-server (CVE-2021-41109)
Summary
Vulnerability in parse-server (CVE-2021-41109). Confidential information can be exposed externally. Exploitable via Parse.User. Mitigation: upgrade to 4.10.4 or later.
Original description
The description as published by the source.
Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to version 4.10.4, for regular (non-LiveQuery) queries, the session token is removed from the response, but for LiveQuery payloads it is currently not. If a user has a LiveQuery subscription on the Parse.User class, all session tokens created during user sign-ups will be broadcast as part of the LiveQuery payload. A patch in version 4.10.4 removes session tokens from the LiveQuery payload. As a workaround, set user.acl(new Parse.ACL()) in a beforeSave trigger to make the user private already on sign-up.
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-41109 has been found in parse-server.
Attackers can target a specific entry point like Parse.User over the network to misuse the product.
Confidential information can be exposed externally.
What to do: upgrade parse-server to 4.10.4 or later.
If unsure, ask your IT team or search "parse-server CVE-2021-41109" on the vendor's site.
CVE-2021-41109 (parse-server) — CWE-200
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: Parse.User
Patched: 4.10.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.
Information disclosure (CWE-200) exists in parse-server. Attackers reach the vulnerable code path via Parse.User without authentication.
Check the vendor advisory for the affected versions of parse-server. Attack surface: Parse.User.
Severity: ?. Confidential information can be exposed externally.
Update to 4.10.4.
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 'parse-server' . 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 'parse-server' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
parse-serverを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade parse-server to 4.10.4ステージング環境で 4.10.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com