rive-app / rive-app/rive-runtime
Requesting private vulnerability reporting be enabled
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.2k
- Forks
- 121
- PR merge metrics
- No merged PRs in 30d
Description
Hi, I found a memory-safety issue in rive-runtime's .riv parser (via dynamic analysis with Runzee, an eBPF-based Android security research tool) that reproduces against your real, shipped Android library and would like to report it responsibly. I noticed this repo doesn't have private vulnerability reporting enabled (Settings > Security > "Privately report a security vulnerability") and there's no SECURITY.md, so there's no self-service private channel right now. Could you enable it, or point me to the right contact so I can send details privately? Happy to wait.
Thanks!
Contributor guide
No contributing guide indexed for this repository
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 in the repository Settings > Security area and review whether private vulnerability reporting can be enabled. Also check whether a SECURITY.md is present; done means providing a private reporting channel or a documented security contact for the reported memory-safety issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, cpp
- Domain
- security
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100