Please Read This If You Read Anything

• We are an open source project source code of the application can be found here https://gitlab.com/upchieve/subway so please ==do NOT bruteforce for the content discovery.== We are not hiding any secrets in directories.
• We are aware of RATE LIMITING issues, any report on this issue would be closed as N/A
• We have several premade user accounts here that you can use.
• If none of those meet your needs, please create accounts using a HackerOne email to help us track security research activity. You can create accounts on UPchieve by using [email protected]

Response Targets

UPchieve will make best efforts to meet the following response timelines for researchers participating in our program:

We’ll try to keep you informed about our progress throughout the process.

Scope

We have listed the assets in scope for this program, however, if you have found a potential vulnerability (excluding the out of scope vulnerabilities listed below), system or asset you believe belongs to UPchieve, please submit it through this program as we would like to hear about it.

In scope vulnerabilities

Technical vulnerabilities or security-related problems in any of our mentioned assets or subdomains. Technical vulnerabilities or security-related problems in our infrastructure.

The following issues are currently considered do not attempt without permission:

• ==Extended testing/attacks of UPchieve servers or infrastructure==
• ==Rate limiting or brute-force attacks on UPchieve backend infrastructure==
• ==Any activity that could lead to the disruption of our service (DoS).==

To request permission, please email [email protected] and mention the details of your test including what endpoint(s) you will be hitting, what type of scan/attack/etc you would like to try, and what you're trying to achieve. We will respond within 2 working days, ideally less to your request. As long as it is reasonably well thought out and we don't see a risk on our end, we will approve the request.

Out of Scope Vulnerabilities

When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug. The following issues are considered out of scope:

• Social engineering or phishing
• Denial of service attacks
• Resource Exhaustion Attacks
• Clickjacking on pages with no sensitive actions
• Cross-Site Request Forgery (CSRF) on Login, Logout pages or pages with no sensitive actions
• Attacks requiring MITM or physical access to a user's device.
• Previously known vulnerable libraries without a working Proof of Concept.
• Missing best practices in SSL/TLS configuration.
• Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
• ==Missing best practices in Content Security Policy.==
• ==Missing HttpOnly or Secure flags on cookies==
• ==Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)==
• Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors).
• Issues that require unlikely user interaction

Disclosure Policy

• Do not discuss reported vulnerabilities outside of the program without express consent from the organization until the issue is fixed.
• Follow HackerOne's disclosure guidelines.
• As an open organization, our policy is to fully disclose all resolved, informative, and not applicable issues, in the interest of openness and transparency for our users.

Safe Harbor

Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you. If legal action is initiated by a third party against you in connection with activities conducted under this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.

Thank you for helping keep UPchieve and our users safe!