Comparison Overview
CASA Saint-Gobain

CASA Saint-Gobain
Rua 25 de Abril, Serzedo - Vila Nova de Gaia, Porto, 4410-014, PT
Last Update: 16/12/2025
A CASA - Claim Accident Service Assistance, é um player completo em termos de reabilitação urbana e reparação de todo o tipo de danos na habitação, com cobertura nacional, sustentado pelo know-how da Saint‐Gobain, líder mundial no habitat sustentável! A CASA representa...

STRABAG
Ortenburger Strasse 27, Spittal/Drau, 9800, AT
Last Update: 01/04/2026
At STRABAG around 86,000 people working on progress at more than 2,400 locations worldwide. Uniqueness and individual strengths characterise both our projects and each of us as individuals. Whether its building construction, civil engineering, road construction, undergr...
Compliance Ranges Comparison

CASA Saint-Gobain







STRABAG






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

CASA Saint-Gobain

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