Comparison Overview
PH Tech

PH Tech
8650 Boul. Guillaume Couture, None, Lévis, Québec, CA, G6V 9G9
Last Update: 01/04/2026
At P.H. Tech, since more than 60 years, we specialize in the design of high-performance PVC windows and patio doors as well as in the PVC profile extrusion for our own door and window systems, assembled and installed by independent manufacturers. P.H. Tech is not just ...

Masco Corporation
17450 College Parkway, Livonia, 48152, US
Last Update: 01/04/2026
Masco Corporation is a global leader in the design, manufacture and distribution of branded home improvement and building products. Our products enhance the way consumers all over the world experience and enjoy their living spaces. Our portfolio of industry-leading bran...
Compliance Ranges Comparison

PH Tech







Masco Corporation






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

PH Tech

Masco Corporation
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.