parse-community / parse-community/parse-server
Improve Security around allowClientClassCreation
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 21.4k
- Forks
- 4.8k
- Avg merge
- 7h 45m
- Merged PRs (30d)
- 11
Description
New Feature / Enhancement Checklist
- I am not disclosing a vulnerability.
- I am not just asking a question.
- I have searched through existing issues.
Current Limitation
Parse Server is designed so that it can be booted up and tested easily. However, there are some default configurations that are insecure, meaning that when a developer transitions to production, they mightn't be aware of the openings which they haven't fixed.
Feature / Enhancement Description
Just like fileUpload, migrate allowClientClassCreation to default to false, expect for the core classes (such as _User).
Or:
Have 2 start scripts:
npm start:dev // allows for any insecure option, such as allowClientClassCreation or mountPlayground
npm start:prod // overrides insecure options
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
Start by tracing how allowClientClassCreation and the existing fileUpload default are handled in Parse Server. Compare that behavior with the proposed npm start:dev and npm start:prod alternatives. Done requires an agreed security policy and implementation for production defaults or separate startup modes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- api, backend, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100