Description

iBOOD looks forward to working with the security community to find security vulnerabilities in order to keep our business and customers safe. A security vulnerability is a weakness in a product, service or system that could allow an attacker to compromise the integrity, availability, or confidentiality of that product, service or system. Thank you in advance for your contribution!

Bounties
Low
Medium
High
Critical
Exceptional
Tier 2
€ 0
€ 50
€ 150
€ 350
€ 500
Up to € 500
Tier 3
€ 0
€ 25
€ 75
€ 175
€ 250
Up to € 250
Domains

my.ibood.com

Tier 2
URL
Tier 3
iOS

api.ibood.com

Tier 3
URL
Tier 3
Android

www.ibood.com

Tier 3
URL

*.forum.ibood.com

No Bounty
URL

Please use the following topic for testing purposes:
http://uk-en.forum.ibood.com/contests/intigriti-comment-test-post-2/

beta.ibood.com

No Bounty
URL

blog.ibood.com

No Bounty
URL

feeds.ibood.com

No Bounty
URL

img.ibood.com

No Bounty
URL
In scope

IMPORTANT: Please use the following topic for testing purposes: http://uk-en.forum.ibood.com/contests/intigriti-comment-test-post-2

We are happy to announce our first bug bounty program! We've done our best to clean most of our known issues and now would like to request your help to spot the once we missed! We are specifically looking for:

  • leaking of personal data
  • horizontal / vertical privilege escalation
  • injection flaws
  • buffer overflow
  • vulnerabilities that destruct data, or introduce an interruption or degradation of our service.
Out of scope

Application

  • Verbose messages/files/directory listings without disclosing any sensitive information
  • CORS misconfiguration on non sensitive endpoints
  • Missing cookie flags
  • Missing security headers
  • Cross-site Request Forgery with no or low impact (login CSRF, logout CSRF, add/remove/edit items in basket, ...)
  • Presence of autocomplete attribute on web forms
  • Reverse tabnabbing
  • Bypassing rate-limits or the non-existence of rate-limits
  • Best practices violations (password complexity, expiration, re-use, etc.)
  • Clickjacking on pages without sensitive actions
  • CSV Injection without demonstrating a vulnerability
  • Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
  • Host Header Injection
  • Username / email enumeration
  • Hyperlink injection/takeovers
  • Mixed content type issues
  • Cross-domain referer leakage
  • Anything related to email spoofing, SPF, DMARC or DKIM
  • E-mail bombing
  • HTTP Request smuggling without any proven impact
  • Homograph attacks
  • XMLRPC enabled
  • Banner grabbing /Version disclosure
  • Open ports without an accompanying proof-of-concept demonstrating vulnerability
  • Weak SSL configurations and SSL/TLS scan reports
  • Not stripping metadata of images
  • Disclosing API keys without proven impact
  • Previously known vulnerable libraries without a working Proof of Concept
  • Arbitrary file upload without proof of the existence of the uploaded file

General

  • In case that a reported vulnerability was already known to the company from their own tests, it will be flagged as a duplicate.
  • Theoretical security issues with no realistic exploit scenario(s) or attack surfaces, or issues that would require complex end user interactions to be exploited, may be excluded or be lowered in severity
  • Spam, social engineering and physical intrusion
  • DoS/DDoS attacks or brute force attacks.
  • Vulnerabilities that are limited to non-current browsers (older than 3 versions) will not be accepted
  • Attacks requiring the usage of shared computers, man in the middle or compromised user accounts
  • Recently disclosed zero-day vulnerabilities in commercial products where no patch or a recent patch (< 2 weeks) is available. We need time to patch our systems just like everyone else - please give us 2 weeks before reporting these types of issues.
  • Attacks requiring unrealistic user interaction

Mobile

  • Shared links leaked through the system clipboard
  • Any URIs leaked because a malicious app has permission to view URIs opened
  • The absence of certificate pinning
  • Sensitive data in URLs/request bodies when protected by TLS
  • Lack of obfuscation
  • Path disclosure in the binary
  • Self-XSS that cannot be used to exploit other users
  • Lack of jailbreak & root detection
  • Crashes due to malformed URL Schemes
  • Lack of binary protection (anti-debugging) controls, mobile SSL pinning
  • Snapshot/Pasteboard leakage
  • Runtime hacking exploits (exploits only possible in a jailbroken environment)
  • API key leakage used for insensitive activities/actions
  • Attacks requiring physical access to the victim's device
  • Attacks requiring installing malicious applications onto the victim's device
Rules of engagement

Our promise to you

  • We are happy to respond to any questions during business hours, please use the button in the right top corner for this
  • We will treat your report as confidential
  • We respect the safe harbour clause that you can find below

Your promise to us

  • Provide detailed but to-the point reproduction steps Include a clear attack scenario. How will this affect us exactly?
  • Remember: quality over quantity!
  • Please do not publicly disclose, discuss or post vulnerabilities without our consent (including PoC's on YouTube and Vimeo)
  • Please do not use automatic scanners -be creative and do it yourself! We cannot accept any submissions found by using automatic scanners. Scanners also won't improve your skills, and can cause a high server load (we'd like to put our time in thanking researchers rather than blocking their IP's 😉)

Safe harbour for researchers

iBOOD.com considers ethical hacking activities conducted consistent with the Researcher Guidelines, the Program description and restrictions (the Terms) to constitute “authorized” conduct under criminal law. iBOOD.com will not pursue civil action or initiate a complaint for accidental, good faith violations, nor will they file a complaint for circumventing technological measures used by us to protect the scope as part of your ethical hacking activities.

If legal action is initiated by a third party against you and you have complied with the Terms, iBOOD.com will take steps to make it known that your actions were conducted in compliance and with our approval.

Severity assessment

Exceptional

  • RCE (Remote Code Execution)

Critical

  • Access to all customer personal data
  • SQL injection

High

  • Stored XSS without user interaction
  • Privilege escalation
  • Authentication bypass on critical infrastructure

Medium

  • XSS
  • CSRF with a significant impact

Low

  • XSS that requires lots of user interaction ( > 3 steps)
  • open redirect
FAQ

Where can we get credentials?

You can self-register on the applications but please don’t forget to use your @intigriti.me address. Be aware that registering your email address will link it to a specific country. If you want to order in a different country you will need a different email alias.

All aboard!
Please log in or sign up on the platform

For obvious reasons we can only allow submissions or applications for our program with a valid intigriti account.

It will only take 2 minutes to create a new one or even less to log in with an existing account, so don't hesitate and let's get started. We would be thrilled to have you as part of our community.

Researchers
last contributors
logo
logo
logo
logo
logo
logo
leaderboard
logo
logo
logo
logo
logo
logo
Overall stats
submissions received
255
average payout
€74
accepted submissions
13
total payouts
€345
Last 90 day response times
avg. time first response
< 24 hours
avg. time to triage
< 2 days
Activity
9/16
iBOOD.com
closed a submission
9/15
logo
created a submission
9/2
iBOOD.com
closed a submission
8/30
logo
created a submission
8/30
iBOOD.com
closed a submission
8/30
iBOOD.com
closed a submission
8/28
logo
created a submission
8/27
logo
created a submission
8/24
iBOOD.com
closed a submission
8/23
logo
created a submission