Description

Law firms and legal departments can connect their cloud environment. Once they connect their cloud environment (Microsoft SharePoint, OneDrive Personal/Business, ...), we will start fetching all Doc/Docx/Dotx/PDF files from the Microsoft Graph API. We start reading these files (contracts) and write the definitions and clauses we found in our PostgreSQL database. Once all this data is in our database, the customer (this tenant) can search for these definitions and clauses in a Word add-in.

Bounties
Low
0.1 - 3.9
Medium
4.0 - 6.9
High
7.0 - 8.9
Critical
9.0 - 9.4
Exceptional
9.5 - 10.0
Tier 2
50
150
600
3,000
4,000
Tier 2
€50 - €4,000
Rules of engagement
Not applicable
Not applicable
Not applicable
Not applicable

By participating in this program, you agree to:

  • Respect the Community Code of Conduct
  • Respect the Intigriti Terms and Conditions
  • Respect the scope of the program
  • Not discuss or disclose vulnerability information without prior written consent (including PoC's on YouTube and Vimeo)
Domains

https://api-dashboard.stag.henchman.io

Tier 2
URL

https://api-search.stag.henchman.io

Tier 2
URL

https://add-in.stag.henchman.io

Tier 2
URL

This is our add-in.

You can authenticate with:
email: wouter+intigriti@henchman.io
password: 7qHVPbNm_MZmdNkc-_nwXJkCTyXu*EfRsK9Pmnn3

Here you can search for the analysed data. You will see this data after your integration is finished.

https://youtu.be/BF1bsN2JpBY

https://auth.stag.henchman.io

Tier 2
URL

https://dashboard.stag.henchman.io

Tier 2
URL

This is our dashboard.

We've created a Intigriti - Bug Bounty Program tenant.

You can authenticate with:
email: wouter+intigriti@henchman.io
password: 7qHVPbNm_MZmdNkc-_nwXJkCTyXu*EfRsK9Pmnn3

Here you can add/remove users and add an integration.

https://youtu.be/BF1bsN2JpBY

https://ops-dashboard.stag.henchman.io

Tier 2
URL

This is our operations dashboard.

You can authenticate with:
email: wouter+intigriti@henchman.io
password: 7qHVPbNm_MZmdNkc-_nwXJkCTyXu*EfRsK9Pmnn3

You will need this to make sure the integration flow goes as smooth as possible. Integration connections that have been made by the customer/tenant on the dashboard will need to be approved here first. Also, this platform will give you extra information about the state of the integration. An integration can only be deleted on the operations dashboard.

https://youtu.be/BF1bsN2JpBY

⚠️ It's important that you use this ops-dashboard only for you own integration flow or to create a company for yourself. Please don't add yourself as a user to another company that you haven't created yourself. This can be in use for other researchers ⚠️

*.henchman.io

No bounty
URL

For the Dashboard, Auth, Add-in and API endpoints - Do NOT test these on production. Please use the staging environments listed in the above domains section.

In scope

⚠️ Do not delete the users / tenants described in this project nor change the password of these accounts ⚠️

We are happy to announce our first bug bounty program!
Help us find those critical and exceptional vulnerabilities, so we can adapt and get better. Remote code executions or data leaks are what we hope to cover.

Below we will have a few point which cover our whole platform scope, going from processing documents, to user Authentication/Authorization, user and company management and searching on data which was processed.

from a user perspective we have:

UI Host Backend Host
Dashboard UI https://dashboard.stag.henchman.io Dashboard API https://api-dashboard.stag.henchman.io
Operations UI https://ops-dashboard.henchman.io/ Ops API https://api-ops.stag.henchman.io/
Login flow NA Auth API https://auth.stag.henchman.io/
Add-in https://add-in.stag.henchman.io/ Search API https://api-search.stag.henchman.io/

This shows us that there is a clear split between exposed services (API’s) and the documents processing pipeline. Also take note that the Ops UI is only used internally and is never exposed to a customer.

Our main priorities lie in testing that processing pipeline which comes close to the system, and the search, testing our schemas and logical segregation.


1. Processing flow -- all the info you need to get started with data
https://youtu.be/BF1bsN2JpBY

This demo will aid you into seting up an integration with a DMS (Document Management System like Google Drive, Sharepoint, …), where you possibly could inject some malicious things into documents from an external system.

We analyse and convert these documents with PDFBox (3.0.0-alpha3) and LibreOffice (7.4.1), after which we add the data to our persistence backend. (PostgreSQL).
What could go wrong:

  • access to other tenants' data
  • SQLi
  • remote code execution
  • whatever you can find to compromise our systems!

We are looking forward to see what your creativity can bring to


2. Search API (add-in)

Check out our search API, where you can, after injecting your documents through our processing pipeline, search results.

  • How does it react to weird data your processed from documents?
  • How does it handle input validation, are there some gaps?

Let us know!


3. Other services

Let us know what you can find on:

  • our Auth flow
  • our Ops dashboard and identity management, be it users or companies and integrations
  • our Dashboard, where our customers can add an integration themselves

All in all, we wish to deliver better and more secure software (yes that marketing fluffiness is also something we strive for) and hope we can count on your help for this.

Keep us on our toes!

https://media.giphy.com/media/dlxZ5qZs91Kx2/giphy.gif

Feedback
Would you like to help us improve our program or have some feedback to share, please send your anonymous feedback here:
Program feedback link
Please note this form will be checked periodically and should not be used for submission or support queries.

dependencies.txt
10/27/2022, 12:39:23 PM
Out of scope

Application

  • API key disclosure without proven business impact
  • Wordpress usernames disclosure
  • Pre-Auth Account takeover/OAuth squatting
  • Self-XSS that cannot be used to exploit other users
  • 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
  • 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 without proven impact/unrealistic user interaction
  • CSV Injection
  • Sessions not being invalidated (logout, enabling 2FA, etc.)
  • Tokens leaked to third parties
  • Anything related to email spoofing, SPF, DMARC or DKIM
  • Content injection without being able to modify the HTML
  • Username/email enumeration
  • Email bombing
  • HTTP Request smuggling without any proven impact
  • Homograph attacks
  • XMLRPC enabled
  • Banner grabbing/Version disclosure
  • Not stripping metadata of files
  • Same-site scripting
  • Subdomain takeover without taking over the subdomain
  • Arbitrary file upload without proof of the existence of the uploaded file
  • Blind SSRF without proven business impact (pingbacks are not sufficient)
  • Disclosed/misconfigured Google Maps API keys
  • Host header injection without proven business 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
  • Spam, social engineering and physical intrusion
  • DoS/DDoS attacks or brute force attacks
  • Vulnerabilities that only work on software that no longer receive security updates
  • Attacks requiring physical access to a victim's computer/device, man in the middle or compromised user accounts
  • Recently discovered zero-day vulnerabilities found in in-scope assets within 14 days after the public release of a patch or mitigation may be reported, but are usually not eligible for a bounty
  • Reports that state that software is out of date/vulnerable without a proof-of-concept
Severity assessment

This program follows Intigriti's contextual CVSS standard

Cool-down period for zero-days
Recently discovered zero-day vulnerabilities found in in-scope assets within 14 days after the public release of a patch or mitigation may be reported, but are usually not eligible for a bounty.

FAQ

Where can we get credentials for the app?

You can find the credentials for the domains in scope in the domain section.

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.

Program specifics
no reputation No collaboration
Researchers
last contributors
logo
logo
logo
logo
logo
logo
leaderboard
logo
logo
logo
logo
logo
logo
Last 90 day response times
avg. time first response
< 16 hours
avg. time to triage
< 2 days
Activity
2/22
Henchman
changed the in scope
2/7
Henchman
changed the out of scope
1/25
Henchman
closed a submission
1/25
logo
created a submission
1/4
Henchman
closed a submission
1/3
logo
created a submission
12/21
Henchman
closed a submission
12/20
logo
created a submission
12/12
Henchman
closed a submission
12/9
logo
created a submission