Upserve is committed to protecting the privacy and security of our users. We recognize the valuable role security researchers play in making our services more secure and are committed to working with you to verify and resolve legitimate security vulnerabilities. We ask that you carefully review this policy and scope to ensure the best experience for all involved.

Important Notes

Do not test with the live upserve.com site. Please review the scope for

details on the test site URL specific for security research

• Do not run automated scans without checking with us first. They are often very noisy and disruptive.

Public Disclosure Policy

Upserve supports public disclosure of most vulnerabilities following resolution. We ask that you not share vulnerability details with anyone other than Upserve or HackerOne prior to approved public disclosure through the HackerOne platform.

• In most cases, Upserve will allow public disclosure of vulnerabilities within 30 days of resolution.
• In some cases, Upserve will request that public disclosure is delayed. (for example, if we need to conduct private notifications first)
• In limited cases, Upserve may request that a report remain private. In these cases, we will maintain open communication with the researcher about why we feel this is important.
• Follow HackerOne's disclosure guidelines.

Report Quality

• Please consider the attack scenario and exploitability of the bug.
• Please provide detailed reports with reproducible steps and demonstrable impact. If the report is not detailed enough to reproduce the issue, the issue will not be eligible for a reward.
• If you’re unsure of the direct impact, but feel you may have found something interesting, please submit a detailed report and ask.
• Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.

Program Rules

• Please check the list of out-of-scope vulnerabilities and known issues before submitting a report.
• Do not run automated scans without checking with us first. They are often very noisy and disruptive.
• Social engineering (e.g. phishing, vishing, smishing) is prohibited.
• Make every effort to avoid privacy violations, destruction of data, and interruption or degradation of our service.
• Only interact with accounts you own or with the explicit permission of the account holder.
• Bounty amounts below are the minimum we will pay per category for bounty eligible assets. We aim to be fair; all reward amounts are at our discretion and based on demonstrable impact.
• If we receive several reports for the same issue, we offer the bounty to the earliest report for which we had enough actionable information to identify the issue.
• Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.

Vulnerability Impact and Rewards

Our rewards are based on the demonstrable impact of a vulnerability. We use CVSS v3 to guide our decisions on vulnerability impact. Things that influence the impact of an issue are the scale of exposure, mitigating factors, and multiplying factors. All valid reports are eligible to receive a HackerOne reputation reward. For assets eligible for a paid bounty, Upserve may provide rewards based on the impact of a vulnerability. Please note these are general guidelines and examples, and that reward decisions are up to the discretion of Upserve.

Critical:

Critical vulnerabilities have a CVSS v3.0 score of 9.0 or higher and they can be readily compromised with publicly available malware, exploits, or techniques.

Examples of issues that Upserve might consider of critical impact include:

• Gaining unauthorized access to any merchant’s account or data (e.g. credit card numbers, transaction information, etc.)
• Gaining unauthorized access to any customer’s account or data (e.g. credit card numbers, etc.)
• Gaining unauthorized access to any production systems (e.g. shell access, code execution, etc.)
• Exposed credentials that could result in access to production systems or deployment pipelines (e.g. API keys, access tokens, etc.)
• The ability to cause monetary impact to Upserve, a merchant, or a customer (e.g. creating orders with a payment method you don't own, issue refunds, manipulating order totals, etc.)

High:

High severity vulnerabilities have a CVSS v3.0 score of 7.0 to 8.9.

Examples of issues that Upserve might consider high impact include:

• Targeted attacks that result in access to an individual merchant or customer’s account or data (e.g. reflected XSS that requires social engineering)
• Direct object references to sensitive information

Medium:

Medium severity vulnerabilities have a CVSS v3.0 score of 4.0 to 6.9.

Examples of issues that Upserve might consider medium impact include:

• Issues that impact less sensitive assets, such as the public marketing sites
• Being able to modify a merchant or customer’s settings without their permission
• Content injection that allows for convincing phishing attacks (e.g. HTML injection or XSS in an unauthenticated domain)
• Open URL redirection

Low:

Low severity vulnerabilities have a CVSS v3.0 score of 0.1 to 3.9.

Examples of issues that Upserve might consider low impact include:

• Leaks of less sensitive information that has a demonstrable impact
• Directory traversal

Test Plans

Read carefully for instructions and tips on testing:

• Upserve Loyalty (https://app.upserve.com/b/swipely-bistro __) is a React application with a Ruby on Rails backend. REST API calls are made to app.upserve.com/c/ and cards.swipely.com. The application allows a consumer to register an account and enroll one or more credit cards into a restaurant's loyalty program. Purchases made by the consumer at the restaurant are tracked in the loyalty program and a reward is given when the consumer's account reaches a specified level. It is not currently possible for researchers to generate sales that apply to the loyalty program. We are interested in vulnerabilities that would allow a consumer to fraudulently add points to their own account or steal points from other accounts. Use the provided test restaurant Swipely Bistro only. Testing on any other restaurant is prohibited without approval from Upserve.

  • To create a customer account, navigate to https://app.upserve.com/b/swipely-bistro __, enter in your email address, enter in a credit card number (either your own or you can use a credit card generator to create a fake one). The application will reject duplicate card numbers.
  • cards.swipely.com provides an endpoint for adding payment cards to the vault. The endpoint returns a token which should not be reversible. This API should not be able to provide back full payment card numbers.

  • Upserve Online Ordering (OLO) (https://app.upserve.com/s/upserve-lounge-test-providence-2 __) is a React application with a Ruby on Rails backend. REST API calls are made to orders.upserve.com and payments.upserve.com. Orders can be submitted to the test restaurant linked in this plan using any valid credit card number. Credit cards will not be charged or authorized with this restaurant. Testing on any other restaurant is prohibited without approval from Upserve.

  • You may create an account or you can place orders without an account

  • You may use any validly formatted credit card number - either your own, or you can use a credit card generator to create a fake one.
  • Orders placed are submitted to the Upserve POS service and will most likely be rejected after 20 minutes unless someone at Upserve is actively working with this test restaurant
  • payments.upserve.com provides an endpoint for adding payment cards to the vault. The endpoint returns a payment method token which is used by the OLO API. The token should not be reversible and should only be usable to the restaurant it was generated for. The payments sandbox in use for testing is very lenient and will allow invalid card numbers to be used. If you think you 've found a bug here we are happy to validate against a live gateway.
  • Upserve.com, RestaurantInsider.com (https://645892349820.vulnerbug.com __) is a Wordpress application. Do not test upserve.com or restaurantinsider.com directly. Please only test https://645892349820.vulnerbug.com/ __. Our primary concern here would be defacement, but there isn’t much sensitive data or functionality here - as such, reward amounts for this property will typically be lower.

• teamhelp.upserve.com is a Wordpress application for internal use by team members. Users are required to sign-in with their Upserve Google account to access the information. There is non-public information on this site. Our primary concern here would be access to non-public information or defacement. Reward amounts for this property will typically be lower than our customer-facing applications.

• Upserve HQ (https://app.upserve.com/partners/ __) is a Ruby on Rails application used by restaurants to view operational, sales, marketing, and finance information.

  • Without credentials, only authentication bypass can be tested. Credentials are provided by invite only at this time (please don't ask).

  • Upserve POS HQ (https://hq.breadcrumb.com/ __) is a Ruby on Rails application used by restaurants to manage their point of sale tablets and view sales reports.

  • Without credentials, only authentication bypass can be tested. Credentials are provided by invite only at this time (please don't ask).

  • Upserve Live Mobile App - This app is for restaurants to view operational and sales information.

  • Without credentials, only authentication bypass can be tested. Credentials are provided by invite only at this time (please don't ask).

  • Upserve POS iPad App - This app is our point of sale app for restaurants.

  • Without credentials, only authentication bypass can be tested. Credentials are provided by invite only at this time (please don't ask).

Out of scope vulnerabilities

The following issues are considered out of scope:

• Wordpress user enumeration
• Clickjacking on pages with no sensitive actions.
• Unauthenticated/logout/login CSRF.
• Attacks requiring MITM or physical access to a user's device.
• Previously known vulnerable libraries without a working Proof of Concept.
• Comma Separated Values (CSV) injection without demonstrating a vulnerability.
• Missing best practices in SSL/TLS configuration.
• Any activity that could lead to the disruption of our service (DoS).
• Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
• Account oracles -- the ability to submit a phone number, email, UUID and receive back a message indicating an Upserve account exists.
• Vulnerabilities as reported by automated tools without additional analysis as to how they're an issue.
• Reports from automated web vulnerability scanners (Acunetix, Vega, etc.) that have not been validated.
• Banner grabbing issues
• Rate limiting issues
• Missing best practices in email configuration (DMARC, SPF, DKIM, etc)

Known Issues

The following issues are already known to our team - please do not submit new reports related to them, as they will be considered duplicates.

• Sessions do not expire after password change/reset
• Attacker can enroll credit cards in another user's loyalty accounts
• XML-RPC available on Wordpress sites (and associated DoS issues)

Safe Harbor

We will not pursue civil action or initiate a complaint to law enforcement for accidental, good faith violations of this policy. We consider activities conducted consistent with this policy to constitute “authorized” conduct under the Computer Fraud and Abuse Act. To the extent your activities are inconsistent with certain restrictions in our Terms & Conditions __, we waive those restrictions for the limited purpose of permitting security research under this policy. We will not bring a DMCA claim against you for circumventing the technological measures we have used to protect the applications in scope.

If legal action is initiated by a third party against you and you have complied with Upserve's bug bounty policy, Upserve will take steps to make it known that your actions were conducted in compliance with this policy.

Please understand that if your security research involves the networks, systems, information, applications, products, or services of another party (which is not us), that third party may determine whether to pursue legal action. We cannot and do not authorize security research in the name of other entities.

We will not share your report with a third-party without your permission and/or gaining their commitment they will not pursue legal action against you. Please note again that we can’t authorize out-of-scope testing in the name of third parties and such testing is beyond the scope of the program.

Please submit a HackerOne report to us before engaging in conduct that may be inconsistent with or unaddressed by this policy.

Thank you for helping keep Upserve and our users safe! If you have a question that is not answered on this page, please contact bugbounty@upserve.com

In order to encourage the adoption of bug bounty programs and promote uniform security best practices across the industry, Upserve reserves no rights in this bug bounty policy and so you are free to copy and modify it for your own purposes.