Comparison Overview
Helifors AS

Helifors AS
Kesk-Sõjamäe, Tallinn, 11415, EE
Last Update: 09/03/2026
From product to solution. We combine the best products in order to offer solutions that meet our customers’ specifications and the needs of end-users. Helifors is Estonian leading wholesaler of electrical, telecom & automation products. We serve the needs of electrical ...

Ferguson
751 Lakefront Commons, Newport News, Virginia, US, 23606
Last Update: 02/04/2026
Since 1953, Ferguson has been a leading source of quality supplies for a variety of industries. We are proud to provide world-class products and services to a customer base that is as vast and varied as our inventory. The professionals we serve help transform the world ...
Compliance Ranges Comparison

Helifors AS







Ferguson






Benchmark & Cyber Underwriting Signals
Incidents vs Wholesale Industry Avg (This Year)
No incidents recorded for Helifors AS in 2026.
Incidents vs Wholesale Industry Avg (This Year)
No incidents recorded for Ferguson in 2026.
Incident History - Helifors AS (X = Date, Y = Severity)
Helifors AS cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Ferguson (X = Date, Y = Severity)
Ferguson cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Helifors AS

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