DRACOON – Bug Bounty Program
Kiteworks’ mission is to empower organizations to effectively manage risk in every send, share, receive and save of sensitive content. To this end, we created a platform that delivers content governance, compliance, and protection to customers. The platform unifies, tracks, controls, and secures sensitive content moving within, into, and out of their organization, significantly improving risk management and ensuring regulatory compliance on all sensitive content communications.
Reward
Program
Hacktivity
Updates
February 2026
- We finished our work on a fully automated account registration process. Please review the "Account access" section in this program. With the switch to the new process, we also fully reset the existing environment. This means, that you need to register again using the new process. Apologies for any inconvenience.
December 2025
- Enabled Leaks and exposed credentials
- Enabled Systemic Issues grid
June 2025
- Added clarification to the bug bounty brief requiring demonstrable impact for XSS reports beyond simple alert pop-ups.
May 2025
- We will move the DRACOON bug bounty program under the Kiteworks umbrella shortly while we do some organisational re-arrangements. This will not have any effect on this program except that the brand Kiteworks will have increased visibility.
- We declared an end of life date for DRACOON Server. As a result we will no longer pay bounty for findings of low or medium severity based on CVSS. The bounty for findings of high or critical severity remain unchanged. This change only affects DRACOON Server and not DRACOON Cloud. This change is reflected in the program description as well as the reward grid introducing a new medium tier for all assets related to DRACOON Server.
DRACOON
DRACOON offers secure file sharing and collaboration services with two products, DRACOON Cloud and DRACOON Server. Both products support built-in end-to-end encryption and offer many features tailored for large organizations, such as a complex roles and permissions system, SSO integration, auditing and reporting features.
With this bug bounty program, we want to reinforce our commitment to security and reward security researchers for helping us protect our customers' data.
Program Rules
DRACOON wants to increase the security of its products by inviting security researchers to analyze the implementation of security measures in its product and to identify existing vulnerabilities. In order to achieve this goal together, it is important to us that the following rules are adhered to.
- (D)DoS attacks on our infrastructure are strictly prohibited. This includes (but is not limited to) all applications, services, servers and network infrastructure.
- Do not carry out load-based attacks (e.g. automated scanners that create a large number of requests).
- Do not interfere with any box that is not listed within the program scope.
- Do not decommission any boxes.
- Do not change network configuration.
- Do not change passwords of accounts (unless it’s your own) or delete other accounts.
- Do not extract information and disclose it if you should gain access to it irregularly.
- Do not alter, modify or delete any information stored in our cloud if you should gain access to it irregularly.
- Do not publish (even partially) any vulnerabilities that are found.
Reward Eligibility
We are happy to thank everyone who submits valid reports to improve the security of our cloud service, however only those that meet the following eligibility requirements may receive a monetary reward:
- You must be the first reporter of a vulnerability.
- The vulnerability must be a qualifying vulnerability (see below).
- Any vulnerability found must be reported no later than 24 hours after discovery and exclusively through http://yeswehack.com.
- The vulnerability report must contain the following elements:
- A clear textual description of the vulnerability, how it can be exploited, its security impact and remediation advice.
- A proof of the exploitation of the vulnerability (e.g. screenshots, proof of concept code).
- The preconditions and steps required to reproduce the issue including code snippets, commands, request information, payloads, etc.
- You must not be a former or current employee of our company or one of its contractors.
- As DRACOON Cloud and DRACOON Server share the majority of the source code, we consider the same attack on both systems in scope as duplicate.
- DRACOON Server has a declared end of life date. This means that we will not pay bounty for findings of low or medium severity based on CVSS.
XSS Reporting Requirements
Please note that for any reports involving Cross-Site Scripting (XSS), a basic proof-of-concept such as a JavaScript alert box (e.g., alert(1)) will not be considered sufficient for triage or reward. To qualify for a valid report, you must demonstrate a clear and actionable impact resulting from the XSS vulnerability. This includes, but is not limited to:
- Performing actions on behalf of another user (e.g., creating a new user account or modifying user settings)
- Exfiltrating sensitive data (e.g., sending authentication cookies or session tokens to an external server)
- Bypassing security controls or escalating privileges
The goal is to understand the real-world risk and exploitability of the issue, so please ensure your report includes a well-documented and impactful demonstration.
DRACOON Infrastructure Overview
Description of services
Services in scope
Core - This service is the heart of the backend. It is responsible for file upload, download, sharing, user and role management.
OAuth - Responsible for user authentication. Implements OAuth2.
S3 Storage - Storage location of binary data. Accessible via internet and heavy use of pre-signed S3 URLs to allow direct transfer between client app and storage.
Media - Responsible for image downscaling (e.g. for thumbnails).
Reporting - Responsible for generating various reports triggered by the user (e.g. reports on user activity). Creates PDF and CSV files.
WebDAV - Proxy service that allows to connect to DRACOON via WebDAV protocol.
Services out of scope
Branding - Allows customers to customize appearance. Manages customer branding configurations (e.g. logo, email signatures).
Signing - Acts as a proxy to our signing partner FP-Sign. Responsible for sending signing requests and storing signed documents in DRACOON.
Description of clients
Clients in scope
Web App - The main web application to access DRACOON via a browser. This is the only full-feature client.
Clients out of scope
Desktop Apps - Sync client for Windows and Mac. Mounts DRACOON as a virtual disk on the end user’s device.
Mobile Apps - Native apps for Android and iOS, that provide a subset of the features.
MS Teams App - App for MS Teams.
Outlook Add-In - Add-In for MS Outlook. Allows to convert attachments to share links.
Swagger UI - Swagger UI is an interactive API documentation. Most services provide a public Swagger UI client. See useful links section.
| Area | Scope Type | Scope URL | DRACOON Cloud | DRACOON Server |
|---|---|---|---|---|
| Backend | Core Service | /api | yes | yes |
| Backend | OAuth Service | /oauth | yes | yes |
| Backend | S3 Storage | https://0-2744452194.s3.nbg01.de.dracoon.io | yes | no |
| Backend | Media Service | /mediaserver | yes | no |
| Backend | Reporting Service | /reporting[/api] | yes | no |
| Backend | WebDAV Proxy | /webdav | yes | yes |
| Frontend | Web App | / | yes | yes |
Useful links
- Bug Bounty Environments:
- DRACOON Cloud: https://bounty-cloud.dracoon.app
- DRACOON Cloud S3 Storage https://0-2744452194.s3.nbg01.de.dracoon.io
- DRACOON Server: https://bounty-server.dracoon.app
- User manuals, knowledge base:
- DRACOON Cloud: https://cloud.support.dracoon.com
- DRACOON Server: https://server.support.dracoon.com
- Public API documentation (SwaggerUI / OpenAPI 3.0):
- DRACOON Cloud
- Core Service: https://bounty-cloud.dracoon.app/api
- Reporting Service: https://bounty-cloud.dracoon.app/reporting/api
- DRACOON Server
- Core Service: https://bounty-server.dracoon.app/api
- DRACOON Cloud
- Public SDKs and crypto implementation: https://github.com/dracoon
- Whitepaper on e2e encryption: https://cloud.support.dracoon.com/hc/en-us/articles/360000986345-Whitepaper-Client-side-Encryption
Reward
| Asset value | CVSS | CVSS | CVSS | CVSS |
|---|---|---|---|---|
| $500 | $1,000 | $3,000 | $5,000 | |
| $0 | $0 | $3,000 | $5,000 |
Systemic issues
In the context of this program, we do not intend to encourage, accept or reward reports of leaks that are not applicable to our program’s scope and policy. To summarize our policy, you may refer to the below table:
Scopes
| Scope | Type | Asset value | Expand rewards grid |
|---|---|---|---|
https://bounty-cloud.dracoon.app/api | API | ||
Low Medium High Critical | |||
https://bounty-cloud.dracoon.app/oauth | Other | ||
Low Medium High Critical | |||
https://0-2744452194.s3.nbg01.de.dracoon.io | Other | ||
Low Medium High Critical | |||
https://bounty-cloud.dracoon.app/mediaserver | Other | ||
Low Medium High Critical | |||
https://bounty-cloud.dracoon.app/reporting/api | API | ||
Low Medium High Critical | |||
https://bounty-cloud.dracoon.app/webdav | Other | ||
Low Medium High Critical | |||
https://bounty-cloud.dracoon.app/ | Web application | ||
Low Medium High Critical | |||
https://bounty-server.dracoon.app/api | API | ||
Low Medium High Critical | |||
https://bounty-server.dracoon.app/oauth | Other | ||
Low Medium High Critical | |||
https://bounty-server.dracoon.app/reporting/api | API | ||
Low Medium High Critical | |||
https://bounty-server.dracoon.app/webdav | Other | ||
Low Medium High Critical | |||
https://bounty-server.dracoon.app/ | Web application | ||
Low Medium High Critical | |||
Out of scopes
- Any other host, tenant or service than the ones explicitly stated.
- www.dracoon.com
- *.dracoon.com
- *.dracoon.net
- *.dracoon.team
- *.dracoon.app (with the exceptions of bounty-cloud.dracoon.app and bounty-server.dracoon.app)
- *.dracoon.io (with the exception of https://0-2744452194.s3.nbg01.de.dracoon.io)
- *.fp-sign.com
- *.usersnap.com
- *.gdata.com
- *.retarus.com
Vulnerability types
Qualifying vulnerabilities
- SQL Injection (SQLi)
- Cross-Site Scripting (XSS)
- Remote Code Execution (RCE)
- Insecure Direct Object Reference (IDOR)
- Horizontal and vertical privilege escalation
- Authentication bypass & broken authentication
- Business Logic Errors vulnerability with real security impact
- Local files access and manipulation (LFI, RFI, XXE, SSRF, XSPA)
- Cross-Origin Resource Sharing (CORS) with real security impact
- Cross-site Request Forgery (CSRF) with real security impact
- Open Redirect
- Exposed secrets, credentials or sensitive information on an asset under our control and affecting at least one of our scopes
- Broken cryptographic implementation with working exploit
- Cleartext Transmission of Sensitive Information (passwords etc.)
Non-qualifying vulnerabilities
- Broken Link/Social media Hijacking
- Tabnabbing
- Missing cookie flags
- Content/Text injections
- Clickjacking/UI redressing
- Denial of Service (DoS) attacks
- Recently disclosed CVEs (less than 30 days sinces patch release)
- CVEs without exploitable vulnerabilities and PoC
- Open ports or services without exploitable vulnerabilities and PoC
- Social engineering of staff or contractors
- Presence of autocomplete attribute on web forms
- Vulnerabilities affecting outdated browsers or platforms
- Self-XSS or XSS that cannot be used to impact other users
- Any hypothetical flaw or best practices without exploitable vulnerabilities and PoC
- SSL/TLS issues (e.g. expired certificates, best practices)
- Unexploitable vulnerabilities (e.g. Self-XSS, XSS or Open Redirect through HTTP headers...)
- Reports with attack scenarios requiring MITM or physical access to victim's device
- Missing security-related HTTP headers which do not lead directly to an exploitable vulnerability and PoC
- Low severity Cross-Site Request Forgery (CSRF) (e.g. Unauthenticated / Logout / Login / Products cart updates...)
- Invalid or missing email security records (e.g. SPF, DKIM, DMARC)
- Session management issues (e.g. lack of expiration, no logout on password change, concurrent sessions)
- Disclosure of information without exploitable vulnerabilities and PoC (e.g. stack traces, path disclosure, directory listings, software versions, IP disclosure, 3rd party secrets, EXIF Metadata, Origin IP)
- CSV injection
- Malicious file upload (e.g. EICAR files, .EXE)
- HTTP Strict Transport Security Header (HSTS)
- Subdomain takeover without a full exploitable vulnerability and PoC or not applicable to the scope
- Blind SSRF without exploitable vulnerabilities and PoC (e.g. DNS & HTTP pingback, Wordpress XMLRPC)
- Lack or bypass of rate-limiting, brute-forcing or captcha issues
- User enumeration (e.g. email, alias, GUID, phone number, common CMS endpoints)
- Weak password policies (e.g. length, complexity, reuse)
- Ability to spam users (email / SMS / direct messages flooding)
- Disclosed or misconfigured public API keys (e.g. Google Maps, Firebase, analytics tools...)
- Password reset token sent via HTTP referer to external services (e.g. analytics / ads platforms)
- Stolen secrets, credentials or information gathered from a third-party asset that we have no control over
- Exposed secrets, credentials or information on an asset under our control that are not applicable to the program’s scope
- Pre-account takeover (e.g. account creation via oAuth)
- GraphQL Introspection is enabled
- Non sensitive information disclosure: stack traces, path disclosure, directory listings, software versions, etc
- Credential stuffing
- Logout and other instances of low-severity Cross-Site Request Forgery
- Enumeration/account oracles: possibility to enumerate phone number, email, GUID, etc. and receive back a message indicating it exists
- Missing security-related HTTP headers which do not lead directly to a vulnerability
- Race condition
Reports of leaks and exposed credentials
In the context of this program, we do not intend to encourage, accept or reward reports of leaks that are not applicable to our program’s scope and policy. To summarize our policy, you may refer to the below table:
Hunting requirements
Account access
You will receive full admin access to the respective systems. Please request an account by filling the following form: https://content.kiteworks.com/af/f-iPR2g5z7jpDeG3frGwE3wW/dracoon-public-bug-bounty-program. We will only create accounts for YesWeHack email alias.
After submitting the form using your YesWeHack email alias, we will create the admin accounts within 24 hours. Please watch out for welcome emails containing initial passwords from the two systems.
User agent
Please append to your user-agent header the following value: ' -bug-bounty-yeswehack '.
Hunters collaboration
When submitting new report, you can add up to 5 collaborators, and define the reward split ratio.
For more information, see help center.
Note: For reports that have already been rewarded, it is not possible to redistribute the rewards.