LocalMonero Whitehat Program For Security Researchers
Responsible disclosure includes:
- 1. Providing us a reasonable amount of time to fix the issue before publishing it elsewhere.
- 2. Making a good faith effort to not leak or destroy any LocalMonero user data.
- 3. Not defrauding LocalMonero users or LocalMonero itself in the process of discovery.
In general, anything which has the potential for financial loss or data breach is of sufficient severity is eligible, including:
- • XSS
- • CSRF
- • Authentication bypass or privilege escalation
- • Click jacking
- • Remote code execution
- • Obtaining user information
- • Accounting errors
- • Lack of password length restrictions
- • Session-related issues (session fixation etc.)
- • Merely showing that a page can be iFramed without finding a link on the page to be click-jacked.
- • Self-XSS
- • Denial of service
- • Spamming
- • Vulnerabilities in third party applications which make use of the LocalMonero API
- • Vulnerabilities which involve privileged access (e.g. rooting a phone) to a victim's device(s)
- • Logout CSRF
- • User existence/enumeration vulnerabilities
- • Password complexity requirements
- • Reports from automated tools or scans (without accompanying demonstration of exploitability)
- • Social engineering attacks against LocalMonero employees or contractors
- • Text-only injection in error pages
- • Automatic hyperlink construction by 3rd party email providers
- • Using email mutations (+, ., etc) to create multiple accounts for a single email
Please note, while we are still a growing startup we are unable to provide enormous compensation.
Please send a detailed step-by-step instruction on how to reproduce the bug to to firstname.lastname@example.org.
By submitting a bug, you agree to be bound by the above rules.
Known issues SHA256.
Thank you for helping keep the Monero community safe!