Comparison Overview
Caf de l'Oise
Caf de l'Oise
2 rue Jules Ferry, Beauvais , 60012, FR
Last Update: 05/03/2026
La Caisse d’allocations Familiales de l’Oise est un organisme de Sécurité sociale de droit privé qui assure une mission de service public La Caf de l’Oise appartient à un réseau composé de 101 caisses à vocation départementale, et compte 5 points d’accueils dans le dé...
National Nuclear Security Administration (NNSA)
1000 Independence Avenue SW, Washington, 20585, US
Last Update: 01/04/2026
Established by Congress in 2000, NNSA is a semi-autonomous agency within the U.S. Department of Energy that protects our nation by designing and delivering a safe, secure, reliable, and effective U.S. nuclear stockpile; forging solutions that enable global security and ...
Compliance Ranges Comparison
Caf de l'Oise
National Nuclear Security Administration (NNSA)
Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for Caf de l'Oise in 2026.
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for National Nuclear Security Administration (NNSA) in 2026.
Incident History - Caf de l'Oise (X = Date, Y = Severity)
Caf de l'Oise cyber incidents detection timeline including parent company and subsidiaries.
Incident History - National Nuclear Security Administration (NNSA) (X = Date, Y = Severity)
National Nuclear Security Administration (NNSA) cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Caf de l'Oise
National Nuclear Security Administration (NNSA)
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.