open-feature / open-feature/cpp-sdk-contrib
[flagd] Checks on incoming FlagSync json structure
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2
- Forks
- 3
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 5
Description
Theoretically incoming messages from the SyncService might be malicious by f.e. deeply nested objects trying to reach stack overflow. We should consider some safety measures during json parsing for such behaviour.
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 locating the FlagSync JSON parsing entry point and the SyncService handling for incoming messages. Determine what safety measures are required for deeply nested objects and define completion criteria around safely handling the described input without stack overflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100