Comparison Overview
Communication Research Center at Boston University

Communication Research Center at Boston University
704 Commonwealth Ave, Boston, Massachusetts, 02215, US
Last Update: 02/04/2026
The Communication Research Center (CRC) at Boston University is the College of Communication’s (COM’s) media research hub. Research is an integral part of faculty and student activities at BU. Researchers at COM use the most advanced theory and methods to examine commun...

PPD
168 3rd Ave, Waltham, 02451, US
Last Update: 01/04/2026
The PPD™ clinical research business of Thermo Fisher Scientific, the world leader in serving science, enables customers to accelerate innovation and drug development through patient-centered strategies and data analytics. Our services, which span multiple therapeutic ar...
Compliance Ranges Comparison

Communication Research Center at Boston University







PPD






Benchmark & Cyber Underwriting Signals
Incidents vs Research Services Industry Avg (This Year)
No incidents recorded for Communication Research Center at Boston University in 2026.
Incidents vs Research Services Industry Avg (This Year)
No incidents recorded for PPD in 2026.
Incident History - Communication Research Center at Boston University (X = Date, Y = Severity)
Communication Research Center at Boston University cyber incidents detection timeline including parent company and subsidiaries.
Incident History - PPD (X = Date, Y = Severity)
PPD cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Communication Research Center at Boston University

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