64648 policies in database
Link to program      
2022-07-08
Mon Espace Santé (MES) logo
Thank
Gift
HOF
Reward

Reward

Mon Espace Santé (MES)

My Health Space

It is an individual digital space, a Virtual Health Notebook, which is open to all French people from the beginning of 2022.

It allows:

  • To store its health data online and replaces the shared medical record (DMP).
  • Keep and file all medical documents.

It also contains:

  • Secure messaging with an address to converse with healthcare professionals.
  • An agenda for medical appointments and other acts.
  • A catalog of applications.
  • The data collected by the connected objects on the condition that the applications used are referenced, that they meet all the security conditions imposed by the French State.
  • Your children's health profiles can be integrated into it.

This site is accessible to all and compatible with all terminals (smartphones, tablets, computers). The Caisse Nationale d'Assurance Maladie (CNAM) and the French Ministry of Solidarity and Health are committed to ensuring the protection, confidentiality and security of all data (administrative and health). Its security and the protection of personal data are guaranteed by the French State, the CNIL, and the CNAM.
Their accommodation is provided in France. Among the features, some have a critical aspect for the application.

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.

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 :

Source of leak is in-scope Source of leak belongs to our organization but is out-of-scope Source of leak does not belong to our organization and is out-of-scope
Impact is in-scope (e.g. valid credentials on an in-scope asset) Eligible Eligible Not Eligible
Impact is out-of-scope (e.g. valid credentials for an out-of-scope asset) Eligible Not Eligible Not Eligible

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 sensitive information leak, DO NOT extract/copy every document or data that is exposed and limit yourself to describe and list what is exposed.

In Scope

Scope Type Scope Name
android_application

play.google.com/store/apps/details?id=fr.assurancemaladie.monespacesante&showAllReviews=true (Android)

api

api.monespacesante.fr

api

editeur.api.monespacesante.fr

api

api.editeur.preprod.monespacesante.fr

api

api.preprod.monespacesante.fr

api

preprod.api.monespacesante.fr

api

preprod.editeur.api.monespacesante.fr

api

www.editeur.api.monespacesante.fr

ios_application

apps.apple.com/fr/app/mon-espace-sant%C3%A9/id1589255019 (iOS)

mobile_applications

am.monespacesante.fr

mobile_applications

editeur.am.monespacesante.fr

mobile_applications

am.editeur.preprod.monespacesante.fr

mobile_applications

am.preprod.monespacesante.fr

mobile_applications

preprod.am.monespacesante.fr

mobile_applications

preprod.editeur.am.monespacesante.fr

mobile_applications

www.am.monespacesante.fr

mobile_applications

www.editeur.am.monespacesante.fr

web_application

www.monespacesante.fr

web_application

admincms.monespacesante.fr

web_application

adminstore.monespacesante.fr

web_application

auth.monespacesante.fr

web_application

cms.monespacesante.fr

web_application

editeurs.monespacesante.fr

web_application

knowage.monespacesante.fr

web_application

support.monespacesante.fr

web_application

auth.preprod.monespacesante.fr

web_application

preprod.auth.monespacesante.fr

web_application

preprod.monespacesante.fr

web_application

preprod1.monespacesante.fr

web_application

preprod2.monespacesante.fr

web_application

securite.monespacesante.fr

web_application

www.preprod.monespacesante.fr

web_application

www.preprod1.monespacesante.fr

web_application

www.preprod2.monespacesante.fr

Out of Scope

Scope Type Scope Name
undefined

Anything that is not explicitely listed as part of the Scope


Firebounty have crawled on 2022-07-08 the program Mon Espace Santé (MES) on the platform Yeswehack.

FireBounty © 2015-2025

Legal notices | Privacy policy