GHSA-jhp4-jvq3-w5xr — parse-dashboard
Fix: parse-community/parse-dashboard@f92a9efGHSA-jhp4-jvq3-w5xr is a CWE-1289 vulnerability in parse-dashboard. A fix is available for parse-dashboard — see the affected versions and patch details below.
Parse Dashboard Has a Cache Key Collision that Leaks Master Key to Read-Only Sessions
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-jhp4-jvq3-w5xr.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
parse-dashboardnpmDescription
Impact
The ConfigKeyCache uses the same cache key for both master key and read-only master key when resolving function-typed keys. Under specific timing conditions, a read-only user can receive the cached full master key, or a regular user can receive the cached read-only master key.
Patches
The fix uses distinct cache keys for master key and read-only master key.
Workarounds
Avoid using function-typed master keys, or remove the agent configuration block from your dashboard configuration.
Resources
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | parse-dashboard | ≥ 7.3.0-alpha.42&&< 9.0.0-alpha.8 | 9.0.0-alpha.8npm install parse-dashboard@9.0.0-alpha.8 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for parse-dashboard, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update parse-dashboard to 9.0.0-alpha.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jhp4-jvq3-w5xr is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-jhp4-jvq3-w5xr can be triaged on real exposure rather than presence alone.
Tailored to GHSA-jhp4-jvq3-w5xr. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-jhp4-jvq3-w5xr in your dependencies?
O3 Security finds GHSA-jhp4-jvq3-w5xr across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.