Comparison Overview
CCBR Clinical Research (Now Bioclinica)

CCBR Clinical Research (Now Bioclinica)
N/A
Last Update: 01/01/2026
CCBR is now Bioclinica. Bioclinica is a specialty services provider that utilizes expertise and technology to create clarity in the clinical trial process. Bioclinica is organized by three business segments to deliver focused service supporting multifaceted technologi...

Fresenius Kabi
Else-Kröner-Straße 1, Bad Homburg, Hessen, DE, 61352
Last Update: 01/04/2026
As a global healthcare company, Fresenius Kabi is Committed to Life. The company’s products, technologies, and services are used for the therapy and care of critically and chronically ill patients. With over 41,000 employees and present in over 100 countries, Fresenius ...
Compliance Ranges Comparison

CCBR Clinical Research (Now Bioclinica)







Fresenius Kabi






Benchmark & Cyber Underwriting Signals
Incidents vs Pharmaceutical Manufacturing Industry Avg (This Year)
No incidents recorded for CCBR Clinical Research (Now Bioclinica) in 2026.
Incidents vs Pharmaceutical Manufacturing Industry Avg (This Year)
No incidents recorded for Fresenius Kabi in 2026.
Incident History - CCBR Clinical Research (Now Bioclinica) (X = Date, Y = Severity)
CCBR Clinical Research (Now Bioclinica) cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Fresenius Kabi (X = Date, Y = Severity)
Fresenius Kabi cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

CCBR Clinical Research (Now Bioclinica)

Fresenius Kabi
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.