Comparison Overview
Robin Hill Farm, Inc. "A Brain Injury Residential Treatment and Rehabilitation Program"
Robin Hill Farm, Inc. "A Brain Injury Residential Treatment and Rehabilitation Program"
Deering, us
Last Update: 26/03/2026
Robin Hill Farm has been providing community-based cognitive rehabilitation for adults with Brain Injuries since 1983. Our programs offer residential treatment, and can be considered a long-term alternative to institutional living, or a short-term step towards return to...
Prisma Health
300 E McBee Ave, Greenville, 29601, US
Last Update: 01/04/2026
Prisma Health is the largest not-for-profit health organization in South Carolina, serving more than 1.2 million patients annually. Our facilities in the Greenville and Columbia surrounding markets are dedicated to improving the health of all South Carolinians through i...
Compliance Ranges Comparison
Robin Hill Farm, Inc. "A Brain Injury Residential Treatment and Rehabilitation Program"
Prisma Health
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Robin Hill Farm, Inc. "A Brain Injury Residential Treatment and Rehabilitation Program" in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Prisma Health in 2026.
Incident History - Robin Hill Farm, Inc. "A Brain Injury Residential Treatment and Rehabilitation Program" (X = Date, Y = Severity)
Robin Hill Farm, Inc. "A Brain Injury Residential Treatment and Rehabilitation Program" cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Prisma Health (X = Date, Y = Severity)
Prisma Health cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Robin Hill Farm, Inc. "A Brain Injury Residential Treatment and Rehabilitation Program"
Prisma Health
FAQ
Latest Global CVEs
Buffer Overflow vulnerability in Systerel S2OPC 1.7.3 allows a remote attacker to cause a denial of service via the Alarm/Conditions wrapper when processing PublishResponse EventNotificationList data
- https://github.com/gff-cw/information/issues/18
- https://github.com/systerel/S2OPC/blob/S2OPC_Toolkit_1.7.3/src/ClientServer/address_space/sopc_event_manager.c
- https://github.com/systerel/S2OPC/blob/S2OPC_Toolkit_1.7.3/src/ClientServer/frontend/client_wrapper/alarm_conditions/libs2opc_client_alarm_conditions.c
- https://github.com/systerel/S2OPC/blob/S2OPC_Toolkit_1.7.3/src/ClientServer/frontend/client_wrapper/internal/state_machine.c
- https://gitlab.com/systerel/S2OPC/-/work_items/1781
Buffer Overflow vulnerability in Systerel S2OPC 1.7.3 allows a remote attacker to cause a denial of service via the LockedStaMac_ProcessMsg_DeleteMonitoredItemsResponse and SOPC_StaMac_NewDeleteMonitoredItems in the client wrapper DeleteMonitoredItems path
- https://github.com/gff-cw/information/issues/16
- https://github.com/systerel/S2OPC/blob/master/samples/ClientServer/client_wrapper/examples/subscribe.c
- https://github.com/systerel/S2OPC/blob/master/src/ClientServer/frontend/client_wrapper/internal/state_machine.c
- https://gitlab.com/systerel/S2OPC/-/work_items/1780
In open62541 1.5.5, a server-side use-after-free exists in the local MonitoredItem callback path. The issue occurs when UA_Subscription_localPublish continues to use the current UA_Notification after a callback invokes UA_Server_deleteMonitoredItem for the current local MonitoredItem. This allows a remote attacker to cause a denial of service.
H5Z__filter_nbit in H5Znbit.c in HDF5 through 2.3.0 dereferences cd_values[0] through cd_values[4] without validating that cd_values is non-NULL or that cd_nelmts is at least 5, the fixed size of the filter's header. This allows attackers to cause a denial of service via a crafted HDF5 file that stores the N-Bit filter pipeline message with zero client-data values, opened and read via H5Dread, e.g. by the h5ls or h5repack tools.
H5O__layout_decode in H5Olayout.c in HDF5 through 2.3.0 does not validate that a chunked dataset's stored chunk-layout dimensionality matches its dataspace rank when an existing dataset is opened, whereas this check is performed only at dataset-creation time. This allows attackers to cause a denial of service (divide-by-zero and application crash in H5S__hyper_iter_get_seq_list in src/H5Shyper.c) via a crafted HDF5 file with mismatched chunk/dataspace ranks that is opened and read via H5Dopen2 and H5Dread, e.g. by the h5repack tool.