Comparison Overview
Operation Medical
Operation Medical
44 Hersha Drive, Harrisburg, 17102, US
Last Update: 08/09/2026
Operation Medical is an organization of volunteers made up of trained medical professionals and other individuals committed to promoting and providing high quality medical care and education to communities that do not have adequate access to medical care. We are based o...
International Committee of the Red Cross - ICRC
19, avenue de la Paix, Geneva, Geneva, CH, 1202
Last Update: 04/04/2026
Established in 1863, the International Committee of the Red Cross (ICRC) works worldwide to provide humanitarian help for people affected by conflict and armed violence and to promote the laws that protect victims of war. An independent and neutral organization, its man...
Compliance Ranges Comparison
Operation Medical
International Committee of the Red Cross - ICRC
Benchmark & Cyber Underwriting Signals
Incidents vs Non-profit Organizations Industry Avg (This Year)
Operation Medical has 33.77% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Non-profit Organizations Industry Avg (This Year)
No incidents recorded for International Committee of the Red Cross - ICRC in 2026.
Incident History - Operation Medical (X = Date, Y = Severity)
Operation Medical cyber incidents detection timeline including parent company and subsidiaries.
Incident History - International Committee of the Red Cross - ICRC (X = Date, Y = Severity)
International Committee of the Red Cross - ICRC cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Operation Medical
International Committee of the Red Cross - ICRC
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.