DINUM - Démarches Simplifiées - Public Bug Bounty Program

About us

The Direction Interministérielle du NUMérique (DINUM)

The Direction Interministérielle du NUMérique (DINUM) is in charge of the French State's digital transformation for the benefit of citizens and civil servants alike, in all its aspects:

• Modernisation of the State's information system
• Quality of digital public services
• Creation of innovative services for citizens
• Design of digital collaborative work tools for agents

It supports public services, advises the government and develops common resources such as the Inter-ministerial State Network (RIE) or the French eIDAS node (FranceConnect).

Démarches Simplifiées

The DINUM is developing the "Démarches Simplifiées" system for the benefit of all French administrations/public organisations. This is a fully online application that allows all organisations with public services missions to create digital procedures in a few minutes and manage users' requests on a dedicated platform.

It also allows citizens to manage and keep track of their own procedures through a dedicated dashboard.

The DINUM Bug Bounty approach

The DINUM considers crucial to work with trusted and qualified security researchers to identify weaknesses in its applications, regardless of the technology used, and improve its assest security by leveraging the YWH community's motivation and skills.

If you believe you have found a security problem in our products or services we'll be happy to hear about it as well as to work with you on fixing it as quickly as possible.

Of course, we expect you to work in a responsible manner given out applications' contexts in order to avoid any interruption of service and to protect the privacy of our users. Thus, please do not try to over-exploit a bug, in doubt please contact us for further guidance.

As the French public state is committed to an open data approach, most of our applications' source codes are publicly available on GitHub . If proposals for fixes and improvements on the concerned GitHub project will be appreciated mind that reporting any security issue through this mean is forbidden.

What kind of data is stored by Démarches Simplifiées?

• All fields in a procedure that contain personal data
• All attachments submitted by users

Regarding testing conditions

How to access the scope/retrieve an account

Two "démarches" will be at your disposal for the purpose of your test :

• https://www.demarches-simplifiees.fr/commencer/public-bug-bounty-1
• https://www.demarches-simplifiees.fr/commencer/public-bug-bounty-2

To ease report management, we kindly ask you to use your YWH aliases (*@yeswehack.ninja) for your main account and subaccounts, you can retrieve your aliases here.

You'll be granted the 'utilisateur' role by default, no 'instructeur' account will be handed out in the framework of this program.

As you'll be working in production, other legitimate/official 'démarches' are out of the scope of this program in order to not impact legitimate users. Thus, mind that any report based on exploitation involving other 'démarches' will be considered as out of scope/won't be eligible for reward.

Where to find our application's code and documentation

The code of the application is open source and is available on GitHub :
https://github.com/demarches-simplifiees/demarches-simplifiees.fr

The code of the encryption brick of the solution is also available on GitHub :
https://github.com/demarches-simplifiees/ds_proxy

Concerning the API, all the documentation is available here :
https://doc.demarches-simplifiees.fr/pour-aller-plus-loin/graphql

The https://doc.demarches-simplifiees.fr/ site contains all the documentation needed to understand how the platform works.

About the DS Proxy scope and its reward grid

DS Proxy is an HTTP streaming encryption proxy. It is used by our application as a mean to provide protection against unauthorized access to shared object storage spaces by storing only encrypted data.

We're willing to offer a higher reward for any vulnerability pertaining to this specific functionality of the application, i.e. this specific reward grid is only applicable to issues related to encryption through this module.

About AgentConnect/FranceConnect

The AgentConnect/FranceConnect authentication feature is out of the scope of this program. If you need to reach out the concerned team you may do so through their public program : https://yeswehack.com/programs/franceconnect-agentconnect-public.

Program rules

Testing Policy and Responsible Disclosure

Please adhere to the following rules while performing research on this program:

• Denial of service (DoS) attacks on our 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, manipulate, or destroy any user data or files in any of our applications/servers.
• Do not copy any files from our applications/servers and disclose them.
• No vulnerability disclosure, full, partial or otherwise, is allowed.

Reward Eligibility and Amount

We 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:

• You must be the first reporter of a vulnerability.
• The vulnerability must be a qualifying vulnerability (see below).
• 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 our organisation, 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 our organisation or one of its contractors.
• 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.
• 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.

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

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 identified outside of our program’s scope, such as:

• Exposed credentials in/from an out-of-scope asset/source
• Sensitive information exposed in/from an out-of-scope asset/source

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

This excludes, but is not limited to:

• Stolen credentials gathered from unidentified sources
• Exposed credentials that are not applicable on the program’s scope
• Exposed GitHub/GitLab (or similar) instance with no direct relation with our program’s scope
• Exposed secrets (e.g. API tokens/keys or other technical credentials) that are not directly related to the program’s scope
• Exposed PII on an out-of-scope asset

To summarize our policy, you may refer to this table :

Important precautions and limitations

As a complement to the Program’s rules and testing policy :

• DO NOT alter compromised accounts by creating, deleting or modifying any data
• DO NOT use compromised accounts to search for post-auth vulnerabilities (they won’t be eligible anyway)
• DO NOT include Personally Identifiable Information (PII) in your report and please REDACT/OBFUSCATE the PII that is part of your PoC (screenshot, server response, JSON file, etc.) as much as possible.
• In case of exposed credentials or secrets, limit yourself to verifying the credentials validity
• In case of sensitivie information leak, DO NOT extract/copy every document or data that is exposed and limit yourself to describe and list what is exposed.