Comparison Overview
UNSW Centre for Social Research in Health

UNSW Centre for Social Research in Health
undefined, Kensington Campus, NSW, 2052, AU
Last Update: 25/04/2026
The Centre for Social Research in Health undertakes and promotes exemplary research in health that informs and strengthens knowledge, policy and practice.

University of Wisconsin-Madison
500 Lincoln Dr, Madison, WI, US, 53706-1380
Last Update: 02/04/2026
In achievement and prestige, the University of Wisconsin–Madison has long been recognized as one of America's great universities. A public, land-grant institution, UW–Madison offers a complete spectrum of liberal arts studies, professional programs and student activitie...
Compliance Ranges Comparison

UNSW Centre for Social Research in Health







University of Wisconsin-Madison






Benchmark & Cyber Underwriting Signals
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for UNSW Centre for Social Research in Health in 2026.
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for University of Wisconsin-Madison in 2026.
Incident History - UNSW Centre for Social Research in Health (X = Date, Y = Severity)
UNSW Centre for Social Research in Health cyber incidents detection timeline including parent company and subsidiaries.
Incident History - University of Wisconsin-Madison (X = Date, Y = Severity)
University of Wisconsin-Madison cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

UNSW Centre for Social Research in Health

University of Wisconsin-Madison
FAQ
Latest Global CVEs
OpenStack Ironic through 38.0.0 may send a username and password to an unexpected remote host when Image Service is configured for HTTP(S) Basic Authentication.
An issue was discovered in OpenStack Keystone before 29.0.3. Tokens obtained via delegated authentication methods (EC2 credentials, application credentials, OAuth1 access tokens, and trusts) are not blocked from creating, modifying, or deleting credentials via the /v3/credentials API. EC2-derived tokens can additionally read credential blobs, exposing TOTP MFA seeds and other secrets. Also, PATCH /v3/credentials does not validate the requested post-update project_id, allowing any delegated token to move a credential to an unauthorized project. All Keystone deployments using delegated authentication are affected.
The administrative password is hashed using a comparatively weak, fast algorithm for the credential store backing one authentication path, and the file containing that hash is written with permissions allowing it to be read by any local user. This is inconsistent with a separate, stronger hashing algorithm used for the same password on another authentication path. A party able to read this file, including a local user or a party with access to a configuration backup, could feasibly recover the underlying password through offline computation, compromising the administrative credential across every path that accepts it.
An example environment-configuration file for a bundled inventory-management component ships with a fixed, publicly-known administrative password. A deployment that copies this example file into active configuration without running the setup routine that regenerates credentials will expose that component's administrative interface to anyone aware of the default value.
A prior update that raised a bundled HTTP client library to a version remediating known vulnerabilities was later reverted, reintroducing the earlier, vulnerable version into a log-processing component. The only code path in that component using the library issues a request to a single fixed, trusted vendor URL at initialization and does not process attacker-controlled input through the library, limiting practical exploitability of the reintroduced version in this context.