Description

Hoplr is the social network for inclusion and citizen engagement. As a social network we consider the safety and continuity of our online services as one of our top priorities. Our team is continually working to optimize our systems and processes, yet despite all the efforts we make to secure our systems, vulnerabilities may still be present. We are happy with your help to further improve our systems and to protect our users and customers even better.

Bounties

Responsible disclosure

Domains

*.hoplr.*

No Bounty
URL
No Bounty
iOS
No Bounty
Android
In scope

We are interested to learn about any potential vulnerabiliity that could impact the security and privacy of our users or customers.
Examples of issues we would like to know more about:

  • Theft of sensitive data
  • Unauthorized modification or deletion of sensitive data
  • Access to other neighbourhoods than the one in which you have a valid membership for. The membership only gives you access to one neighbourhood.
  • Engage with neighbourhoods on behalf of cities or other customers
  • DOS on the level of neighbourhood. Posting content that prevents the neighbourhood (Messages) feed from loading. No request flooding and nothing that causes the website to go down

Info

  • Social Network (www.hoplr.com): Citizens use Hoplr to share goods and services, organize neighbourhood activities, report problems, find lost pets, meet new neighbours, discuss safety, participate in local policy making and so much more.
  • Service Dashboard (services.hoplr.com): Hoplr offers the public sector -local authorities, local utility services, project developers and any local organisation that brings non-commercial value to citizens -a service dashboard to engage with local communities.

Important

Access codes to register an accepted user account in test neighbourhoods can be requested when logged in by using the request credentials button in the upper right corner of our program's page.

Always create a Hoplr account with your @intigriti.me address

More info can be found on: https://go.intigriti.com/intigritime

Out scope

Application

  • Verbose messages/files/directory listings without disclosing any sensitive information
  • Self-XSS that cannot be used to exploit other users
  • CORS misconfiguration on non sensitive endpoints
  • Missing cookie flags on non sensitive cookies
  • Missing security headers which do not present an immediate security vulnerability
  • Cross-site Request Forgery with no or low impact
  • 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
  • Host Header Injection
  • Sessions not being invalidated (logout, enabling 2FA, ..)
  • Hyperlink injection/takeovers
  • Mixed content type issues
  • Cross-domain referer leakage
  • Anything related to email spoofing, SPF, DMARC or DKIM
  • Content injection
  • Username / email enumeration
  • 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

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. We make an exception on the level of neighbourhood. This means posting content that causes the neighbourhood feed (Messages) to be unavailable. Request flooding is still not allowed.
  • 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
  • Access to a neighbourhood with someone else's address and using the regular "Find my neighbourhood" flow on the website or in the app

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
  • 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, please use the button in the right top corner for this.
  • 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 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

Hoplr considers ethical hacking activities conducted consistent with the Researcher Guidelines, the Program description and restrictions (the Terms) to constitute “authorized” conduct under criminal law. Hoplr 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, Hoplr 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

High

  • Stored XSS without user interaction
  • Privilege escalation
  • Authentication bypass on critical infrastructure
  • Posting content that prevents the neighbourhood feed from loading

Medium

  • XSS
  • CSRF with a significant impact

Low

  • XSS that requires lots of user interaction ( > 3 steps)
  • CSRF with a very limited impact
  • Open redirect
FAQ

Where can we get credentials for the app?

You can use the get credentials button in the right top corner to request credentials that are ready to use! Feel free to reach out to support if you have any issue with these credentials.

All aboard!
Please login or register 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 login 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.

Program specifics
ID check required
Reputation points
Triage
Quick stats
submissions received
41
average payout
N/A
accepted submissions
23
total payouts
N/A
Activity
5/20
Hoplr
closed a submission
5/20
logo
abhishek00
created a submission
5/11
Hoplr
closed a submission
5/11
logo
mrvincere
created a submission
5/11
Hoplr
closed a submission
5/11
Hoplr
accepted a submission
5/8
Hoplr
closed a submission
5/7
logo
erdy232
created a submission
5/7
logo
mrvincere
created a submission
4/28
Hoplr
closed a submission