Comparison Overview
Quaker Windows & Doors

Quaker Windows & Doors
504 U. S. Hwy. 63 South, P.O. Box 128, Freeburg, MO, US, 65035
Last Update: 02/04/2026
Quaker Window Products Company, Inc. has been a leader in the window and door industry since 1949. We're known nationwide for manufacturing top quality windows and doors at competitive prices, which has been our trademark business philosophy since the company began. Qua...

Ambuja Cements Limited
Elegant Business Park, Off Andheri Kurla Road,, Mumbai, 400059, IN
Last Update: 02/04/2026
Ambuja Cements Ltd. is among the leading cement companies in India. It is a member of the Adani Group - the largest and fastest-growing portfolio of diversified sustainable businesses. Ambuja Cement is known for its hassle-free, home-building solutions. Its unique produ...
Compliance Ranges Comparison

Quaker Windows & Doors







Ambuja Cements Limited






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

Quaker Windows & Doors

Ambuja Cements Limited
FAQ
Latest Global CVEs
The GOOSE subscriber component improperly validates the UTC timestamp field in unauthenticated IEC 61850 GOOSE (EtherType 0x88B8) Layer-2 multicast messages. A specially crafted GOOSE frame containing an undersized timestamp field can trigger a heap out-of-bounds read during message processing, causing the process to crash and resulting in a denial-of-service condition.
OpenClaw Dashboard contains a stored cross-site scripting vulnerability that allows unauthenticated remote attackers to execute arbitrary JavaScript in the administrator's browser session by injecting HTML markup into agent transcript messages processed through the sessions API. Attackers can craft a message containing inline event handler payloads such as an img tag with an onerror attribute within the 60-character rendering budget, which is stored in the session transcript and interpolated unsanitized into innerHTML on the default landing page, allowing theft of session tokens and unauthorized calls to authenticated administrative endpoints including agent instruction file modification.
MeshCentral 1.1.21 contains a cross-site WebSocket hijacking protection bypass vulnerability that allows unauthenticated remote attackers to hijack authenticated administrator sessions by exploiting an unconditional early return in the CheckWebServerOriginName() function within webserver.js when self-signed certificates are in use. Attackers can open cross-origin WebSocket connections to any of the twelve WebSocket endpoints, send crafted action commands to exfiltrate the server sessionKey used to sign session cookies, forge session tokens as arbitrary users, and gain full remote control of all managed devices governed by the MeshCentral instance.
The GOOSE parser contains an off-by-one boundary-handling flaw that can be triggered by a single unauthenticated Layer-2 multicast frame on the process bus. When specific GOOSE message fields are processed, the parser advances its internal buffer position incorrectly, resulting in a heap out-of-bounds read. On affected platforms, this condition reliably terminates the subscriber process and causes a denial-of-service.
The GOOSE payload parser contains a boundary handling flaw that can be triggered by a single unauthenticated Layer 2 multicast frame on the process bus. When processing specific payload fields, an attacker controlled inner element length may exceed its enclosing length, causing the parser to over read by one byte. This out-of-bounds read reliably terminates the subscriber process, resulting in a denial-of-service condition.