Coordinated disclosure policy
Mercury-Redstone Research LLC looks for security vulnerabilities in widely used software, mostly open source. This page sets out what we do when we find one.
We report privately first
We report each vulnerability privately to the maintainers or vendor of the affected software, through the channel they ask researchers to use, such as a security policy, a security contact or a bug bounty program. If there is no stated channel, we ask the maintainers for a private one.
Details stay confidential
Until a fix or an advisory is published, we share the details only with the people working on the fix.
Deadline
Our default deadline is 90 days from the day we send the report.
- When a fix is under way at the deadline, we extend it once, by up to 30 days, so the fix can ship first.
- If the vulnerability is being exploited, the deadline is 7 days.
- If there is still no fix at the deadline, we may publish an advisory then.
Advisories and credit
After a fix is released, we publish an advisory on our advisories page. It credits everyone who helped, unless they ask not to be named.
CVE identifiers
We ask for a CVE identifier for each vulnerability we report.
Payment
We never ask for payment in exchange for a report, or for keeping its details private. Where the vendor or project runs a bug bounty program, we may accept a reward under the program's terms.
Contact
Questions about this policy: research@mercuryredstone.org