Comparison Overview
Optus Satellite and Space Systems

Optus Satellite and Space Systems
N/A
Last Update: 16/04/2026
Optus Satellite and Space Systems is Australia’s only geostationary satellite owner and operator, with five satellites currently in orbit providing satellite services across Australia and New Zealand and to McMurdo Sound in the Antarctic. Optus has more than 35 years...

NAVAL GROUP
40-42 rue du docteur FInlay, Paris cedex 15, 75732, FR
Last Update: 29/03/2026
As an international naval defence player, Naval Group is a partner for countries seeking to maintain control of their maritime sovereignty. Naval Group develops innovative solutions to meet its customers’ requirements. The group is present throughout the entire life cyc...
Compliance Ranges Comparison

Optus Satellite and Space Systems







NAVAL GROUP






Benchmark & Cyber Underwriting Signals
Incidents vs Defense and Space Manufacturing Industry Avg (This Year)
No incidents recorded for Optus Satellite and Space Systems in 2026.
Incidents vs Defense and Space Manufacturing Industry Avg (This Year)
NAVAL GROUP has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Optus Satellite and Space Systems (X = Date, Y = Severity)
Optus Satellite and Space Systems cyber incidents detection timeline including parent company and subsidiaries.
Incident History - NAVAL GROUP (X = Date, Y = Severity)
NAVAL GROUP cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Optus Satellite and Space Systems

NAVAL GROUP
FAQ
Latest Global CVEs
The GOOSE subscriber component improperly validates the UTC timestamp field in unauthenticated IEC 61850 GOOSE (EtherType 0x88B8) Layer-2 multicast messages. A specially crafted GOOSE frame containing an undersized timestamp field can trigger a heap out-of-bounds read during message processing, causing the process to crash and resulting in a denial-of-service condition.
OpenClaw Dashboard contains a stored cross-site scripting vulnerability that allows unauthenticated remote attackers to execute arbitrary JavaScript in the administrator's browser session by injecting HTML markup into agent transcript messages processed through the sessions API. Attackers can craft a message containing inline event handler payloads such as an img tag with an onerror attribute within the 60-character rendering budget, which is stored in the session transcript and interpolated unsanitized into innerHTML on the default landing page, allowing theft of session tokens and unauthorized calls to authenticated administrative endpoints including agent instruction file modification.
MeshCentral 1.1.21 contains a cross-site WebSocket hijacking protection bypass vulnerability that allows unauthenticated remote attackers to hijack authenticated administrator sessions by exploiting an unconditional early return in the CheckWebServerOriginName() function within webserver.js when self-signed certificates are in use. Attackers can open cross-origin WebSocket connections to any of the twelve WebSocket endpoints, send crafted action commands to exfiltrate the server sessionKey used to sign session cookies, forge session tokens as arbitrary users, and gain full remote control of all managed devices governed by the MeshCentral instance.
The GOOSE parser contains an off-by-one boundary-handling flaw that can be triggered by a single unauthenticated Layer-2 multicast frame on the process bus. When specific GOOSE message fields are processed, the parser advances its internal buffer position incorrectly, resulting in a heap out-of-bounds read. On affected platforms, this condition reliably terminates the subscriber process and causes a denial-of-service.
The GOOSE payload parser contains a boundary handling flaw that can be triggered by a single unauthenticated Layer 2 multicast frame on the process bus. When processing specific payload fields, an attacker controlled inner element length may exceed its enclosing length, causing the parser to over read by one byte. This out-of-bounds read reliably terminates the subscriber process, resulting in a denial-of-service condition.