Comparison Overview
Secrétariat à la réforme des institutions démocratiques, à l’accès à l’information et à la laïcité
Secrétariat à la réforme des institutions démocratiques, à l’accès à l’information et à la laïcité
875 Rue Grande-Allée E, Québec, G1R 4Y8, CA
Last Update: 05/02/2026
Le Secrétariat à la réforme des institutions démocratiques, à l’accès à l’information et à la laïcité est un secrétariat de mission du ministère du Conseil exécutif. Il est chargé de conseiller les autorités gouvernementales sur les sujets suivants : • l’accès à l’info...
European Commission
Rue de la loi, Brussels, 1049, BE
Last Update: 04/04/2026
The Commission represents and upholds the interests of the EU as a whole, and is independent of national governments. The European Commission prepares legislation for adoption by the Council (representing the member countries) and the Parliament (representing the citiz...
Compliance Ranges Comparison
Secrétariat à la réforme des institutions démocratiques, à l’accès à l’information et à la laïcité
European Commission
Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for Secrétariat à la réforme des institutions démocratiques, à l’accès à l’information et à la laïcité in 2026.
Incidents vs Government Administration Industry Avg (This Year)
European Commission has 482.52% more incidents than the average of all companies with at least one recorded incident.
Incident History - Secrétariat à la réforme des institutions démocratiques, à l’accès à l’information et à la laïcité (X = Date, Y = Severity)
Secrétariat à la réforme des institutions démocratiques, à l’accès à l’information et à la laïcité cyber incidents detection timeline including parent company and subsidiaries.
Incident History - European Commission (X = Date, Y = Severity)
European Commission cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Secrétariat à la réforme des institutions démocratiques, à l’accès à l’information et à la laïcité
European Commission
FAQ
Latest Global CVEs
OpenStack Ironic through 38.0.0 may send a username and password to an unexpected remote host when Image Service is configured for HTTP(S) Basic Authentication.
An issue was discovered in OpenStack Keystone before 29.0.3. Tokens obtained via delegated authentication methods (EC2 credentials, application credentials, OAuth1 access tokens, and trusts) are not blocked from creating, modifying, or deleting credentials via the /v3/credentials API. EC2-derived tokens can additionally read credential blobs, exposing TOTP MFA seeds and other secrets. Also, PATCH /v3/credentials does not validate the requested post-update project_id, allowing any delegated token to move a credential to an unauthorized project. All Keystone deployments using delegated authentication are affected.
The administrative password is hashed using a comparatively weak, fast algorithm for the credential store backing one authentication path, and the file containing that hash is written with permissions allowing it to be read by any local user. This is inconsistent with a separate, stronger hashing algorithm used for the same password on another authentication path. A party able to read this file, including a local user or a party with access to a configuration backup, could feasibly recover the underlying password through offline computation, compromising the administrative credential across every path that accepts it.
An example environment-configuration file for a bundled inventory-management component ships with a fixed, publicly-known administrative password. A deployment that copies this example file into active configuration without running the setup routine that regenerates credentials will expose that component's administrative interface to anyone aware of the default value.
A prior update that raised a bundled HTTP client library to a version remediating known vulnerabilities was later reverted, reintroducing the earlier, vulnerable version into a log-processing component. The only code path in that component using the library issues a request to a single fixed, trusted vendor URL at initialization and does not process attacker-controlled input through the library, limiting practical exploitability of the reintroduced version in this context.