Comparison Overview
One Child Every Child

One Child Every Child
University of Calgary 2500 University Drive NW , calgary, CA
Last Update: 11/03/2026
A Canada-first research initiative with a vision for all children to be healthy, empowered and thriving. One Child Every Child creates evidence that embraces the diversity of need, social and medical circumstances as well as systemic barriers facing children and famili...

University of Alabama at Birmingham
Administration Bldg Suite 1070, BIRMINGHAM, 35294-0110, US
Last Update: 02/04/2026
Known for its innovative and interdisciplinary approach to education at both the graduate and undergraduate levels, the University of Alabama at Birmingham, a part of the University of Alabama System, is an internationally renowned research university and academic medic...
Compliance Ranges Comparison

One Child Every Child







University of Alabama at Birmingham






Benchmark & Cyber Underwriting Signals
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for One Child Every Child in 2026.
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for University of Alabama at Birmingham in 2026.
Incident History - One Child Every Child (X = Date, Y = Severity)
One Child Every Child cyber incidents detection timeline including parent company and subsidiaries.
Incident History - University of Alabama at Birmingham (X = Date, Y = Severity)
University of Alabama at Birmingham cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

One Child Every Child

University of Alabama at Birmingham
FAQ
Latest Global CVEs
Uncontrolled Resource Consumption (CWE-400) in Kibana can lead to denial of service via Excessive Allocation (CAPEC-130). A low-privileged authenticated user can send a specially crafted request to a Kibana machine learning feature, causing the server to exhaust available memory and become unavailable to all users.
Uncontrolled Resource Consumption (CWE-400) in Kibana can lead to denial of service via Excessive Allocation (CAPEC-130). An authenticated attacker with low-privilege access can trigger a denial of service condition in Kibana by sending a specially crafted, oversized request payload. Processing this user-supplied input requires resource-intensive memory allocation that can exhaust the available heap memory in the Kibana process, causing it to crash and become unavailable to all users.
Authorization Bypass Through User-Controlled Key (CWE-639) in Kibana can lead to information disclosure via user-supplied identifiers that reference scheduled query result data from Kibana Spaces the requester is not authorized to access.
Incorrect Authorization (CWE-863) in Kibana can lead to integrity compromise of Machine Learning audit and notification records via Accessing Functionality Not Properly Constrained by ACLs (CAPEC-1). A vulnerability exists in Kibana's Machine Learning functionality where a Machine Learning management endpoint performs an insufficient authorization check. The endpoint validates only a coarse privilege level but does not verify that the requesting user has access to the specific Machine Learning job or notification resources provided in the request. As a result, a low-privileged user with Machine Learning access in any Kibana space can manipulate Machine Learning audit and notification records for arbitrary jobs—including jobs in other spaces or belonging to other users—by leveraging Kibana's internally elevated credentials to write to restricted Machine Learning system indices that the user cannot access directly.
Uncontrolled Recursion (CWE-674) in Elasticsearch can lead to denial of service via a specially crafted search request submitted by a low-privileged authenticated user. A user with read-level index access can submit a request that triggers unbounded recursive processing within the Elasticsearch query evaluation component, causing a fatal error that terminates the affected node. In single-node deployments, this results in complete service outage; in multi-node clusters, it causes repeated node restarts and sustained availability degradation.