Responsible disclosure policy
How to report a vulnerability to us, and how we report the vulnerabilities we find to others.
Reporting a vulnerability to us
This part of the policy covers vulnerabilities in our own open-source projects, such as Rewind IL2CPP Decompiler, and in this website.
How to report
Email security@wyrden.co.uk. Please report privately: do not describe the vulnerability in a public issue, pull request or post.
What to include
- The project or web address affected, and the version or commit you tested.
- A description of the vulnerability and what an attacker could do with it.
- The steps needed to reproduce it, or a proof of concept.
- A suggested fix or mitigation, if you have one.
What happens next
We acknowledge reports within 5 working days. Please give us the chance to fix the vulnerability before you publish any details.
How we report vulnerabilities to others
When we find a vulnerability in an open-source project, we report it and help get it fixed. Three principles apply every time.
- Authorised testing only. We only test systems and code we are authorised to test.
- Private report first. We report our findings privately to the maintainers first.
- Publication after a fix. We publish details only after a fix is available or the maintainers agree to disclosure.
Response timelines
- Reports sent to us: we acknowledge them within 5 working days.
- Findings we report to others: our default embargo is 60 days.
Contact
Send reports and questions about this policy to security@wyrden.co.uk. The same contact details are published in machine-readable form at /.well-known/security.txt.