All domains/properties of Ibotta are in scope. Please take care when testing on production not to compromise the functioning of any Ibotta assets or users on the platform.
Ibotta continuously pushes out new code. The web APIs are updated daily, and the mobile app is updated bi-weekly. In the event you don't find anything today, there may be something present tomorrow. This is a great opportunity for Ibotta and the researcher community to work together to find vulnerabilities!
This program adheres to the Bugcrowd Vulnerability Rating Taxonomy for the prioritization of findings.
|$||iOS, Android, API||Web|
Researchers can self register for an account using your @bugcrowdninja.com email address. For more info regarding @bugcrowdninja email addresses, see here.
Researchers will need to have a rewards account on any of these grocery chains. These will not be provisioned by Bugcrowd or Ibotta.
The below documentation contains information regarding how to initiate and use the flow of the application, and API endpoint data and examples. We also have included a video on how to initiate and use the flow.
- Documentation 1: https://drive.google.com/open?id=1gpi1L7TYLSwlQZYBRKaLNvW_2vlwPOn9aofIGmrFKCM
- Documentation 2: https://docs.google.com/document/d/1amiO1LztvjELEEPwkCNh4t2KUG-gMlY3uqMe4X1CUPM/edit?usp=sharing
- Video: https://drive.google.com/a/bugcrowd.com/file/d/1-vB5NZHOIgxBHF2Gbq0-UsD5Yer5Y2Xv/view?usp=sharing
Ibotta is currently for US use only. International researchers are welcome to test against Ibotta assets but must do so through a US IP address (through a self provisioned proxy/vpn).
- Any ability for an attacker to sniff Grocery retailers credentials entered into Ibotta.
- All phone logs, especially exceptions, need to be verified to not include credentials.
- Check for plaintext customer sensitive information sent to 3rd party from our endpoints.
- Input validation for database access for protection against injection.
- Test the restriction of HTTP methods to those we are in control of, or any attack vector against our endpoints.
- 2FA bypass and/or compromising account integrity.
- Cashout threshold and value manipulation.
- The mobile apps are both native
- Servers are Ruby/Rails on Ubuntu
- Hosted on AWS, API endpoints behind Elastic LoadBalancer
- Infrastructure includes Memcache, Redis and MySQL
A key use case for the Ibotta application is cashing out. For testing cash out in this program please be aware of the following:
- Paypal, Venmo, and giftcard cashout methods are live. Because of this, accounts will not be funded again.
- Cashout thresholds are reduced for the bugcrowd provisioned accounts to facilitate testing.
- SMS authentication is enabled for all accounts. Because of fraud scoring, VoIP numbers (Google Voice, etc) may be blocked.
- Critical requests are rate-limited and geoip filtered. Requests from outside the US are not likely to be allowed.
- No attacks/tests of any kind should be performed on the Grocery websites/properties
- Creating counterfeit receipts and barcodes
- Double submission of receipts
- Other customer-support situations
- Denial of Service via high rate requests or other nonstandard requests
- Lack of source code obfuscation (ios-class-guard, ProGuard) for mobile apps
When conducting vulnerability research according to this policy, we consider this research to be:
- Authorized in accordance with the Computer Fraud and Abuse Act (CFAA) (and/or similar state laws), and we will not initiate or support legal action against you for accidental, good faith violations of this policy;
- Exempt from the Digital Millennium Copyright Act (DMCA), and we will not bring a claim against you for circumvention of technology controls;
- Exempt from restrictions in our Terms & Conditions that would interfere with conducting security research, and we waive those restrictions on a limited basis for work done under this policy; and
- Lawful, helpful to the overall security of the Internet, and conducted in good faith.
- You are expected, as always, to comply with all applicable laws.
If at any time you have concerns or are uncertain whether your security research is consistent with this policy, please inquire via email@example.com before going any further.