Comparison Overview
Michigan Gaming Control Board

Michigan Gaming Control Board
3062 W Grand Blvd, Detroit, 48202, US
Last Update: 13/11/2025
The Michigan Gaming Control Board provides for the licensing, regulation and control of casino gaming operations at the Detroit commercial casinos. It also licenses and regulates the casinos' gaming equipment manufacturers and distributors, suppliers and employees. Add...

CONICET
Godoy Cruz 2290, CABA, C1425FQB, AR
Last Update: 02/04/2026
El Consejo Nacional de Investigaciones Científicas y Técnicas (CONICET) es el principal organismo dedicado a la promoción de la ciencia y la tecnología en la Argentina. Su actividad se desarrolla en cuatro grandes áreas: • Ciencias agrarias, ingeniería y de materiales •...
Compliance Ranges Comparison

Michigan Gaming Control Board







CONICET






Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for Michigan Gaming Control Board in 2026.
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for CONICET in 2026.
Incident History - Michigan Gaming Control Board (X = Date, Y = Severity)
Michigan Gaming Control Board cyber incidents detection timeline including parent company and subsidiaries.
Incident History - CONICET (X = Date, Y = Severity)
CONICET cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Michigan Gaming Control Board

CONICET
FAQ
Latest Global CVEs
A vulnerability was detected in mathurvishal CloudClassroom-PHP-Project up to 5dadec098bfbbf3300d60c3494db3fb95b66e7be. This impacts an unknown function of the file viewresult.php. Performing a manipulation of the argument seno results in sql injection. Remote exploitation of the attack is possible. The exploit is now public and may be used. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The vendor was contacted early about this disclosure but did not respond in any way.
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Kibana can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)