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
An authenticated user with the read role may read limited amounts of uninitialized stack memory via specially-crafted issuances of the filemd5 command
The $_internalApplyOplogUpdate aggregation pipeline stage can be used to execute a document diff containing a malformed binary diff to return memory out-of-bounds or crash the server. $_internalApplyOplogUpdate can be executed by any authenticated user with access to the aggregate command.
An authorized user could trigger a server crash by running a query with a 2dsphere index on a field that stores a GeoJSON GeometryCollection containing a Polygon with a strict-winding CRS. Strict-winding polygons are intentionally unsupported for indexing, but the guard that rejects them does not inspect members of a GeometryCollection, allowing the unsafe path to be reached which ends with an ensuing null-pointer dereference.
The ldapQueryPassword parameter, when set through the runtime setParameter command, will log the new password to the mongod.log file in plain text.
An authenticated user can cause a MongoDB server to crash or return incorrect results by creating documents that interfere with internal metadata processing during query execution. This stems from insufficient separation between user-controlled document fields and internal metadata in certain execution paths.