Comparison Overview
Oregon Health & Science University

Oregon Health & Science University
3181 SW Sam Jackson Park Rd, Portland, Oregon, US, 97239
Last Update: 30/03/2026
At OHSU, we deliver breakthroughs for better health. We're driven by the belief that better health starts with innovations in the lab, in the classroom, at the bedside and in our communities. From cancer to Alzheimer's to cardiovascular care, we collaborate every day ...

Aveanna Healthcare
400 Interstate North Pkwy SE, Atlanta, 30339, US
Last Update: 30/03/2026
About Aveanna It all started with a simple idea: How can we help people live better lives by providing better homecare? That idea became a company called Aveanna, dedicated to bringing new possibilities and new hope to those we serve. At Aveanna, we believe that the ul...
Compliance Ranges Comparison

Oregon Health & Science University







Aveanna Healthcare






Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Oregon Health & Science University in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Aveanna Healthcare in 2026.
Incident History - Oregon Health & Science University (X = Date, Y = Severity)
Oregon Health & Science University cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Aveanna Healthcare (X = Date, Y = Severity)
Aveanna Healthcare cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Oregon Health & Science University

Aveanna Healthcare
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.