Comparison Overview
Industrie Reply US

Industrie Reply US
745 McClintock Dr, Burr Ridge, Illinois, 60527, US
Last Update: 20/12/2025
Industrie Reply is the Reply Group company focused on delivering innovative technology-based solutions to address our Customers’ most complex Supply and Value Chain needs. Industrie Reply specializes in three major areas including Supply Chain Execution (SCE), Customer ...

Ferrari
Abetone inferiore, Maranello, 41053, IT
Last Update: 11/08/2026
Ferrari's story officially began in 1947 when its first road car, the 125 S, emerged from the gate of no. 4 Via Abetone Inferiore in Maranello. The iconic two-seater went on to win the Rome Grand Prix later that year and shortly thereafter was developed into a refined G...
Compliance Ranges Comparison

Industrie Reply US







Ferrari






Benchmark & Cyber Underwriting Signals
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for Industrie Reply US in 2026.
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for Ferrari in 2026.
Incident History - Industrie Reply US (X = Date, Y = Severity)
Industrie Reply US cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Ferrari (X = Date, Y = Severity)
Ferrari cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Industrie Reply US

Ferrari
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.