ZECIBLE PUBLIC BUG BOUNTY PROGRAM

Rules

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, 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

Known behaviours (not eligible)

The following behaviours are intended. Reports that only describe them will be closed without reward.

ywh.comptage.zecible.fr - counting tool

• The counting tool is public on purpose: without an account, anyone can build a targeting, get counts, breakdowns and prices, and upload a list of criteria (postal codes, cities, company IDs...). This applies to the pages and to the AJAX calls behind them.
• The login form protects the customer area (orders, extractions, saved targetings), not the counting tool.
• Counts, breakdowns, prices and reference lists (cities, population, activity codes, legal forms...) are aggregated or public data. Obtaining contact records requires a customer account.

ywh.fichiers.zecible.fr - file transfer

• Sending a file is public on purpose: anyone can upload and send a file without an account.
• An upload is only eligible if it leads to code execution or gives access to a file sent by someone else.

All scopes

• Anti-CSRF tokens are not an authentication mechanism: a read-only call accepted without one, or a token present in the page it protects, is not a vulnerability by itself.
• A missing access control is only eligible if it gives access to data or actions that the application reserves for customers, administrators or other users.

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"

Out of scope

• All domains or subdomains not listed in the above list of 'Scopes'

Qualifying vulnerabilities

• SQL Injection (SQLi)
• Cross-Site Scripting (XSS) with real security impact
• 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