Comparison Overview
ArcelorMittal Mines et Infrastructure Canada

ArcelorMittal Mines et Infrastructure Canada
1010 Rue de Serigny, Longueuil, QC, J4K 5G7, CA
Last Update: 02/04/2026
Bienvenue dans notre univers gigantesque ! ArcelorMittal Exploitation minière Canada s.e.n.c. (AMEM) et ArcelorMittal Infrastructure Canada s.e.n.c. (AMIC) font partie du Groupe ArcelorMittal, numéro un de l’acier qui figure aussi parmi les cinq plus grands producteurs...

BHP
171 Collins Street, Melbourne, 3000, AU
Last Update: 03/08/2026
We are supplying the resources the world needs to help build a better, clearer future. Copper for renewable energy. Potash for sustainable farming. Iron ore and metallurgical coal for the steel needed for global infrastructure and the energy transition. #FutureIsClear ...
Compliance Ranges Comparison

ArcelorMittal Mines et Infrastructure Canada







BHP






Benchmark & Cyber Underwriting Signals
Incidents vs Mining Industry Avg (This Year)
No incidents recorded for ArcelorMittal Mines et Infrastructure Canada in 2026.
Incidents vs Mining Industry Avg (This Year)
BHP has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - ArcelorMittal Mines et Infrastructure Canada (X = Date, Y = Severity)
ArcelorMittal Mines et Infrastructure Canada cyber incidents detection timeline including parent company and subsidiaries.
Incident History - BHP (X = Date, Y = Severity)
BHP cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

ArcelorMittal Mines et Infrastructure Canada

BHP
FAQ
Latest Global CVEs
In OpenStack Ironic before 38.0.1, the autodetect deploy interface may fail to run cleaning immediately after enrollment with, or changing to, the autodetect deploy interface.
A flaw was found in Red Hat Quay. A user with FEATURE_BUILD_SUPPORT enabled and repository write access can exploit a Server-Side Request Forgery (SSRF) vulnerability within the build API. This allows the user to provide a malicious URL, causing the Quay builder to make requests to internal network addresses. Such an action could lead to the disclosure of sensitive internal information.
A flaw was found in Red Hat Quay's exported logs feature. An unauthenticated attacker with a valid file ID could download exported action logs without proper authorization. While file IDs are complex, they can be intercepted from plaintext email or webhook callbacks. This vulnerability leads to information disclosure, potentially exposing sensitive data such as usernames, email addresses, IP addresses, and action-specific metadata.
A flaw was found in Red Hat Quay's Stripe billing webhook handler. This vulnerability allows an unauthenticated attacker to forge billing events by sending crafted JSON requests to the `/webhooks/stripe` endpoint without validating the Stripe-Signature header. Successful exploitation can lead to the unauthorized resetting of a namespace's build quota to its maximum and trigger unsolicited billing emails to namespace administrators.
A flaw was found in Red Hat Quay. When the SECURITY_SCANNER_V4_PSK (pre-shared key) is not set, a remote unauthenticated attacker can send POST requests to the security scanner notification endpoint. This allows the attacker to flood the notification queue and inject path traversal characters into Clair API URL paths. The primary consequence is worker resource exhaustion and blind path manipulation on the configured Clair host, potentially leading to a denial of service.