Comparison Overview
The Problem Lab at the University of Waterloo
The Problem Lab at the University of Waterloo
200 University Ave W, Waterloo, Ontario, N2L 3G1, CA
Last Update: 26/04/2026
The Problem Lab identifies and understands important problems to create innovations with disruptive economic and social consequence. We help established organizations, newly created ventures, and aspiring entrepreneurs recognize obstacles. We work with businesses, publ...
York University
4700 Keele Street, Toronto, Toronto, on, CA, M3J 1P3
Last Update: 12/09/2026
York University is a diverse community of students, faculty, and staff driving positive change. As one of the largest post-secondary communities in the world and with a uniquely global perspective, we are driven by passion and purpose as part of a forward-thinking co...
Compliance Ranges Comparison
The Problem Lab at the University of Waterloo
York University
Benchmark & Cyber Underwriting Signals
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for The Problem Lab at the University of Waterloo in 2026.
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for York University in 2026.
Incident History - The Problem Lab at the University of Waterloo (X = Date, Y = Severity)
The Problem Lab at the University of Waterloo cyber incidents detection timeline including parent company and subsidiaries.
Incident History - York University (X = Date, Y = Severity)
York University cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
The Problem Lab at the University of Waterloo
York University
FAQ
Latest Global CVEs
HTTP/2 servers could end up crashing due to inadvertently modifying its HPACK encoder concurrently. This happens because the server modifies the HPACK encoder from two goroutines without synchronization: one uses the encoder to encode a HEADERS frame as part of a response sent to a client and the other modifies the encoder's table size when handling a SETTINGS frame containing SETTINGS_HEADER_TABLE_SIZE that a client sends. A malicious client can repeatedly send a request while changing the header table size to crash the server.
Multiple ECH outer extension references are not permitted under RFC 9849; previously, a client could send a well-crafted packet that could trigger memory exhaustion in the server process by specifying multiple references. We now reject these as malformed and curb the memory amplification vector as a result.
A trusted template author may have previously written a valid template wherein the use of the 'yield' keyword would not be correctly escaped. We now ensure that valid keyword uses are escaped and non-keyword uses are not escaped.
Improper certificate validation in Microsoft Partner Center allows an unauthorized attacker to elevate privileges over a network.
Authorization bypass through user-controlled key in Microsoft Bookings allows an unauthorized attacker to elevate privileges over a network.