Comparison Overview
CJW Medical Center

CJW Medical Center
7101 Jahnke Road, None, Richmond, Virginia, US, 23225
Last Update: 15/02/2026
Chippenham Hospital has provided quality healthcare services since 1972, giving patient's access to highly-trained physicians and advanced technology. With more than 50 years of pioneering healthcare, our 460+ bed hospital is one of the region's leading acute care facil...

Johnson & Johnson
New Brunswick, NJ, US, 08903
Last Update: 20/05/2026
At Johnson & Johnson, we believe health is everything. Our strength in healthcare innovation empowers us to build a world where complex diseases are prevented, treated, and cured, where treatments are smarter and less invasive, and solutions are personal. Through our ex...
Compliance Ranges Comparison

CJW Medical Center







Johnson & Johnson






Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for CJW Medical Center in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
Johnson & Johnson has 85.19% more incidents than the average of all companies with at least one recorded incident.
Incident History - CJW Medical Center (X = Date, Y = Severity)
CJW Medical Center cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Johnson & Johnson (X = Date, Y = Severity)
Johnson & Johnson cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

CJW Medical Center

Johnson & Johnson
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.