{"title":"VINCI SA - Public program","slug":"vincisa-public-program","rules":"## About\n\n### VINCI\n\nVINCI is a world leader in concessions, energy and construction sector.\n\nSecurity is very important to us, this Bug Bounty program shall help us ensure the good level of security of our external assets (VINCI Holding scope).\n\n### VINCI's public Bug Bounty program\n\nThis program concerns our main public web sites, including some applications allowing user enrollment (grey box testing).\n\n\n## Program Rules\n\n### Testing Policy and Responsible Disclosure\n\nPlease adhere to the following rules while performing research on this program:\n- Use the User Agent mentionned below to hunt on this bug bounty program !\n- Denial of service (DoS) attacks on VINCI applications, servers, networks or infrastructure are strictly forbidden.\n- Avoid tests that could cause degradation or interruption of our services.\n- Do not use automated scanners or tools that generate large amount of network traffic.\n- Do not leak, manipulate, or destroy any user data or files in any of our applications\/servers.\n- Do not copy any files from our applications\/servers and disclose them.\n- No vulnerability disclosure, full, partial or otherwise, is allowed.\n\n### Reward Eligibility\n\nWe are happy to thank everyone who submits valid reports which help us improve our security, however only those that meet the following eligibility requirements may receive a monetary reward:\n- You must be the first reporter of a vulnerability.\n- The vulnerability must be a qualifying vulnerability (see below).\n- The report must contain the following elements:\n\t- Clear textual description of the vulnerability, how it can be exploited, the security impact it has on the application, its users and our organisation, and remediation advice on fixing the vulnerability\n\t- Proof of exploitation: screenshots demonstrating the exploit was performed, and showing the final impact\n\t- Provide complete steps with the necessary information to reproduce the exploit, including (if necessary) code snippets, payloads, commands etc\n- You must not break any of the testing policy rules listed above.\n- You must not be a former or current employee of our organisation or one of its contractors.\n- If you find the same vulnerability several times, please create only one report and eventually use comments. You'll be rewarded according to your findings.\n- The triage team will use the \"One Fix One Reward\" process: if two or more endpoints\/forms use the same code base and a single fix can be deployed to fix all the other weaknesses, only one endpoint will be considered as eligible for a reward and other reports will be closed as Informative\/Duplicate.\n\nReward amounts are based on:\n- Reward grid of the report's scope\n- CVSS scoring and actual business impact of the vulnerability upon performing risk analysis\n\n## Additional provision and testing conditions\n\n### Regarding accounts\n\nNo accounts will be provided in the framework of this program but you're welcome nonetheless to self-register whenever possible on our applications. \n\nIf you do self-register, please use your YesWeHack aliases to create your accounts as it will help us triage your report more easily and greatly speed up the process. You can retrieve your aliases [here](https:\/\/yeswehack.com\/user\/my-yeswehack\/email-alias).\n\n### Regarding Forms and contact\/reservation features \n\nPlease use your YWH aliases (*@yeswehack.ninja) whenever testing forms or contact features and, if possible, append the following message to free input fields (e.g. message body or comment) :\n\n*[Bug Bounty, please ignore - Contact VINCI Cybersecurity audit if needed]*\n\nIt'll help us triage your reports more seamlessly.\n\n### Regarding shared code base and framework\n\nPlease note that some of our scopes may share the same framework\/code base which means that any given vulnerability might be found on several scopes but is likely to necessitate only one fix on our end. In such a case your findings might be considered as duplicates and thus won't be eligible for reward.\n\nNonetheless, you're more than welcome to check if your findings apply to other scopes and if they do not share the same root cause\/necessitate several fixes on our side you'll be rewarded accordingly.\n\n### Regarding third parties solutions\n\nSome of our assets are based on third parties solution even though specific developments were undertaken.\n \nThus, for such applications, we're interested in any vulnerability pertaining to configuration\/settings issues or to our proprietary code but mind that vulnerabilities related to our providers' platforms\/solutions\/modules might not be eligible for rewards as it's not under our management nor responsibility.\n\n\n## Reports of leaks and exposed credentials\n\nIn the context of this program, we do not intend to encourage, accept or reward reports of leaks or exposed credentials. \nWe will only consider vulnerabilities or leaks that are identified directly on the scope of this program. \n\nAlso, in order not to encourage dark and grey economies, in particular the purchase, resale and trade of identifiers or stolen information, as well as all types of dangerous behaviour (e.g. social engineering, ...), we will not accept or reward any report based on information whose source is not the result of failure on the part of our organization or one of our employees\/service providers.\n\nThis excludes, but is not limited to:\n- Stolen credentials gathered from unidentified sources\n- Exposed credentials on an out-of-scope assets\n- Exposed GitHub\/GitLab (or similar) instance \n- Exposed secrets (e.g. API tokens\/keys or other technical credentials) \n- Exposed PII on an out-of-scope asset\n\nTo summarize our policy, you may refer to this table :\n\n| | **Source of leak is in-scope** | **Source of leak is out-of-scope** |\n| --- | --- | --- |\n| **Impact is in-scope (e.g. valid credentials on an in-scope asset)** | Eligible| Not Eligible|\n| **Impact is out-of-scope (e.g. valid credentials for an out-of-scope asset)** | Eligible | Not Eligible|\n\nImpacted asset must be under VINCI SA's responsability.","rules_html":"

About<\/h2>\n

VINCI<\/h3>\n

VINCI is a world leader in concessions, energy and construction sector.<\/p>\n

Security is very important to us, this Bug Bounty program shall help us ensure the good level of security of our external assets (VINCI Holding scope).<\/p>\n

VINCI's public Bug Bounty program<\/h3>\n

This program concerns our main public web sites, including some applications allowing user enrollment (grey box testing).<\/p>\n

Program Rules<\/h2>\n

Testing Policy and Responsible Disclosure<\/h3>\n

Please adhere to the following rules while performing research on this program:<\/p>\n