ZECIBLE PUBLIC BUG BOUNTY PROGRAM
Zecible provides companies with a selection of prospecting files of professionals and individuals
Reward
Program
Hacktivity
About
ZECIBLE
ZECIBLE is a company that delivers many services to its customers. Security is very important to us and this Bug Bounty program shall help us meet highest industry standards to offer the most secure service and experience to all parties.
Program Rules
Testing Policy, Responsible Disclosure
Please adhere to the following rules while performing research on this program:
- Make sure to apply hunting requirements policy, specifically User-Agent and VPN so that our teams know the detected activity is related to this program. If not, you might be blocked from our assets due to our security protocols.
- Denial of service (DoS) attacks on ZECIBLE applications, servers, networks or infrastructure are strictly forbidden.
- Avoid tests that could cause degradation or interruption of our services.
- Do not use automated scanners or tools that generate large amount of network traffic
- Do not leak, copy, manipulate, or destroy any user data or files in any of our applications/servers.
- No vulnerability disclosure, full, partial or otherwise, is allowed.
Reward Eligibility
We are happy to thank everyone who submits valid reports which help us improve the security of ZECIBLE, 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
- The report must contain the following elements:
- Clear textual description of the vulnerability, how it can be exploited, the security impact it has on the application, its users and ZECIBLE, and remediation advice on fixing the vulnerability
- Proof of exploitation: screenshots demonstrating the exploit was performed, and showing the final impact
- Provide complete steps with the necessary information to reproduce the exploit, including (if necessary) code snippets, payloads, commands etc
- You must not break any of the testing policy rules listed above
- You must not be a former or current employee of ZECIBLE or one of its contractors.
Reward amounts are based on:
- Reward grid of the report's scope
- CVSS scoring and actual business impact of the vulnerability upon performing risk analysis
Complements about our scopes
ZECIBLE Scope
Important information about our scopes:
- When testing contact forms or any other interaction with our teams, please use your YesWeHack email aliases which are available here and include keywords such as "Bug Bounty"
Reward
Asset value | CVSS | CVSS | CVSS | CVSS |
---|---|---|---|---|
€100 | €200 | €1,500 | €2,000 |
Systemic issues
We appreciate all valid reports submitted to our program that enhance our security. However, please note that if a similar issue has already been reported by another hunter, the reward will be decreasing according to these percentages.
Scopes
Scope | Type | Asset value | Expand rewards grid |
---|---|---|---|
serveur12.notebleue.com | Web application | ||
Low Medium High Critical | |||
ywh.comptage.zecible.fr | Web application | ||
Low Medium High Critical | |||
ywh.static.zecible.fr | Web application | ||
Low Medium High Critical | |||
ywh.fichiers.zecible.fr | Web application | ||
Low Medium High Critical | |||
ywh.mydata.zecible.fr | Web application | ||
Low Medium High Critical | |||
ywh.admin.zecible.fr | Web application | ||
Low Medium High Critical | |||
ywh.api.zecible.fr | Web application | ||
Low Medium High Critical | |||
ywh.dev.zecible.fr | Web application | ||
Low Medium High Critical | |||
ywh.crons.zecible.fr | Web application | ||
Low Medium High Critical | |||
ywh.routage.zecible.fr | Web application | ||
Low Medium High Critical | |||
ywh.update.zecible.fr | Web application | ||
Low Medium High Critical | |||
odoo14.notebleue.pro | Web application | ||
Low Medium High Critical | |||
registre.notebleue.pro | Web application | ||
Low Medium High Critical | |||
svn.notebleue.pro | Web application | ||
Low Medium High Critical | |||
todo.notebleue.pro | Web application | ||
Low Medium High Critical | |||
webtoolbox.notebleue.pro | Web application | ||
Low Medium High Critical | |||
cam.notebleue.pro | Web application | ||
Low Medium High Critical |
Out of scopes
- All domains or subdomains not listed in the above list of 'Scopes'
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
- Exposed secrets, credentials or sensitive information on an asset under our control and affecting at least one of our scopes
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
- Open Redirect
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
Self-register
ZECIBLE Scope
- You can self-register wherever it is allowed.
- Please use your YesWeHack email aliases which are available here for account creation.
User agent
Please append to your user-agent header the following value: ' {{your_username}} '.
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.