DINUM - ProConnect Identité - 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).

ProConnect Identity

DINUM is developing the "ProConnect Identity" system. This is a fully online application that authenticates users via the OIDC protocol, and provides access to other applications.

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.

Regarding testing conditions

How to access the scope/retrieve an account

To test the ProConnect Identity log-in scenario, you must use our dedicated application : https://test.identite.proconnect.gouv.fr. This application is a mock, it is OUT of the scope of the hunting program. It integrates the ProConnect Identity log-in button, that redirects you to the https://identite-sandbox.proconnect.gouv.fr platform which is the scope of the hunting program.

This platform uses actual open data for the organization data.

It is however not bound to any production environment.

You can thus create any user account by providing any SIRET number and using either a disposable e-mail address (like @yopmail.com that you can access here: https://yopmail.com) or your @yeswehack.ninja.

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/numerique-gouv/proconnect-identite

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.

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.