parse-community / parse-community/parse-dashboard
Parse Dashboard has Insecure Content Security
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 3.8k
- Forks
- 1.4k
- PR merge metrics
- No merged PRs in 30d
Description
New Issue Checklist
- I am not disclosing a vulnerability.
- I am not just asking a question.
- I have searched through existing issues.
- I can reproduce the issue with the latest versions of Parse Server and Parse Dashboard.
Issue Description
Parse Dashboard cannot work with secure CSPs as the dashboard uses inline scripts, styles, etc.
Steps to reproduce
Create an express app with strict CORS, and mount dashboard
Actual Outcome
Lots of CORS errors
Expected Outcome
No cors
Related:
https://community.parseplatform.org/t/parse-dashboard-5-0-0-insecure-contentsecuritypolicy-csp/3121
https://community.parseplatform.org/t/dashboard-site-being-flagged-as-unsafe-by-google-safe-browsing/2872/13
Environment
Dashboard
- Parse Dashboard version:
FILL_THIS_OUT - Browser (Safari, Chrome, Firefox, Edge, etc.):
FILL_THIS_OUT - Browser version:
FILL_THIS_OUT
Server
- Parse Server version:
FILL_THIS_OUT - Operating system:
FILL_THIS_OUT - Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc):
FILL_THIS_OUT
Database
- System (MongoDB or Postgres):
FILL_THIS_OUT - Database version:
FILL_THIS_OUT - Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc):
FILL_THIS_OUT
Logs
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No repository files or tests are named. Start by reproducing the issue by mounting Parse Dashboard in an Express app with strict CSP and CORS settings, then inspect the browser errors and related discussion. Done means the dashboard works under the stated secure policy without the reported inline-content or CORS errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- express, javascript
- Domain
- frontend, security, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100