Details

Disclosure Policy

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.

Scope

We are looking for vulnerabilities in the source codes of the Aspen projects.

Rewards

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.

Exclusions

While researching, we'd like to ask you to refrain from:

Denial of service
Spamming
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.

Disclosure Policy

Exclusions

While researching, we'd like to ask you to refrain from:

Denial of service

Spamming

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.