Comparison Overview
Kepler Communications Inc.

Kepler Communications Inc.
24 Ward St, Toronto, M6H 4A6, CA
Last Update: 17/03/2026
We are delivering on-orbit data at lightspeed with a constellation of satellites designed to act as Internet exchange points for space-to-space data relay. Headquartered in downtown Toronto, Kepler is vertically integrated with an in-house production facility, designin...

PT. Indosat Tbk
Jl. Medan Merdeka Barat No. 21 Jakarta 10110, Indonesia, Jakarta Pusat, 10110, ID
Last Update: 19/09/2026
Indosat Ooredoo Hutchison (IDX: ISAT) ("IOH"), are here with our vision to become the most preferred digital telecommunications company of Indonesia. The IOH merger combines two highly complementary businesses between PT Indosat Tbk (“Indosat Ooredoo”) and PT Hutchison ...
Compliance Ranges Comparison

Kepler Communications Inc.







PT. Indosat Tbk






Benchmark & Cyber Underwriting Signals
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for Kepler Communications Inc. in 2026.
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for PT. Indosat Tbk in 2026.
Incident History - Kepler Communications Inc. (X = Date, Y = Severity)
Kepler Communications Inc. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - PT. Indosat Tbk (X = Date, Y = Severity)
PT. Indosat Tbk cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Kepler Communications Inc.

PT. Indosat Tbk
FAQ
Latest Global CVEs
Omni C20 lacks proper certificate validation which could allow an attacker to perform a man-in-the-middle attack which could allow them to execute arbitrary code.
Omni C20 uses hard-coded credentials that could allow an attacker to monitor log files to obtain credentials to access information like mapping data.
The affected products are vulnerable to command injection attack that could allow an unauthenticated attacker to execute system commands during the pairing process.
The Botslab G980H dash camera firmware contains an authentication vulnerability in the root account exposed through the device's UART interface. The affected account does not require a password before granting access to a privileged system interface, and the interface also displays the device's WiFi password during startup. An unauthenticated attacker with physical access to the device could connect to the UART interface, obtain root privileges, and recover the WiFi password.
The Botslab G980H dash camera firmware generates the default WiFi password using predictable device information, portions of which are advertised by the product. An unauthenticated attacker within WiFi range could potentially determine the remaining password characters through limited guessing and gain unauthorized access to the device network.