Comparison Overview
ASCO Power Technologies

ASCO Power Technologies
160 Park Avenue, Florham Park, New Jersey, 07932, US
Last Update: 21/03/2026
ASCO Power Technologies has provided power reliability solutions for more than 125 years. It’s our commitment to innovation that makes our power products and service solutions indispensable in mission-critical functions in different industries. We design, manufacture,...

Bharat Heavy Electricals Limited
Siri Fort Road, New Delhi, 110049, IN
Last Update: 01/04/2026
Established in 1964, BHEL is one of India's largest engineering and manufacturing enterprises in the energy and infrastructure sectors, and a leading power equipment manufacturer globally. BHEL serves the core sectors of the economy and provides a comprehensive portfoli...
Compliance Ranges Comparison

ASCO Power Technologies







Bharat Heavy Electricals Limited






Benchmark & Cyber Underwriting Signals
Incidents vs Appliances, Electrical, and Electronics Manufacturing Industry Avg (This Year)
No incidents recorded for ASCO Power Technologies in 2026.
Incidents vs Appliances, Electrical, and Electronics Manufacturing Industry Avg (This Year)
No incidents recorded for Bharat Heavy Electricals Limited in 2026.
Incident History - ASCO Power Technologies (X = Date, Y = Severity)
ASCO Power Technologies cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Bharat Heavy Electricals Limited (X = Date, Y = Severity)
Bharat Heavy Electricals Limited cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

ASCO Power Technologies

Bharat Heavy Electricals Limited
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.