Comparison Overview
Astro

Astro
All Asia Broadcast Centre, Technology Park Malaysia, Bukit Jalil, Kuala Lumpur, MY, 57000
Last Update: 02/04/2026
At Astro Malaysia Holdings Berhad 201101004392 (932533-V), we believe in the power of stories to bring people together. For decades, we have been at the heart of Malaysian homes, creating moments of joy, laughter and connection. Today, we are proud to serve 5.3 million ...

Universal Orlando Resort
1000 Universal Studios Plaza, Orlando, 32819, US
Last Update: 15/09/2026
For years, we’ve been creating a legacy of unforgettable experiences for our Guests. Our Guests are immersed into the sights and sounds of some of the greatest movies and most legendary stories, and our Team Members are the ones who help make those incredible experience...
Compliance Ranges Comparison

Astro







Universal Orlando Resort






Benchmark & Cyber Underwriting Signals
Incidents vs Entertainment Providers Industry Avg (This Year)
No incidents recorded for Astro in 2026.
Incidents vs Entertainment Providers Industry Avg (This Year)
No incidents recorded for Universal Orlando Resort in 2026.
Incident History - Astro (X = Date, Y = Severity)
Astro cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Universal Orlando Resort (X = Date, Y = Severity)
Universal Orlando Resort cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Astro

Universal Orlando Resort
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)