No technology is perfect, and we believe that working with skilled security researchers across the globe is crucial in identifying weaknesses in any technology. If you believe you've found a security issue in Aspen, we encourage you to notify us. We welcome working with you to resolve the issue promptly.
Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.
Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.
Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or with explicit permission of the account holder.
We are primarily looking for vulnerabilities in the framework itself (https://github.com/AspenWeb). Vulnerabilities in aspen.io (http://aspen.io) will also be considered.
At this time, we are not awarding bounties or cash rewards for reported vulnerabilities. However, researchers will earn HackerOne reputation based on the merit of reported vulnerabilities, which may help qualify them for private bug bounty programs in the future.
Please submit your security issue to Aspen via HackerOne (https://hackerone.com/aspen/). Please provide as much detail as you can (URLs, etc.) and the steps to reproduce the issue. We commit to responding to your report as soon as possible!
While researching, we'd like to ask you to refrain from:
* Denial of service
* Social engineering (including phishing) of Aspen maintainers
⚠️ The following issue types are excluded from scope:
* Network level Denial of Service (DoS/DDoS) vulnerabilities.
* Low severity issues that can be detected with tools such as Hardenize and SecurityHeaders.io.
* XSS issues that affect only outdated browsers.
* Content injection issues.
* Cross-site Request Forgery (CSRF) with minimal security implications (Logout CSRF, etc.).
* Missing cookie flags on non-security-sensitive cookies.
* UI and UX bugs and spelling mistakes.
* CSV injection.
* 401 injection.
* Host header issues without an accompanying proof-of-concept demonstrating vulnerability.
* Open ports without an accompanying proof-of-concept demonstrating vulnerability.
* Banner grabbing issues (figuring out what web server we use, etc.).
* Clickjacking with minimal security implications.
* Output from automated scans - please manually verify issues and include a valid proof of concept.
* Any vulnerability with a CVSS 3 score lower than 4.0, unless it can be combined with other vulnerabilities to achieve a higher score.
aspen.io's email infrastructure may not always follow all best practices to the letter, we ask you not to send us reports about missing best practices concerning email. However, reports of vulnerabilities are welcome.
Thank you for helping keep Aspen and our users safe!
Hall of Fame