Comparison Overview
Prime Communications MX

Prime Communications MX
Isabel la Católica 39, Centro Histórico de la Ciudad de México, Centro, Centro, 06000, MX
Last Update: 21/04/2026
Somos el socio comercial más importante de AT&T, desde 2019 contamos con presencia en gran parte del territorio nacional, actualmente contamos con más de 590 tiendas y continuamos con un exitoso crecimiento Hemos sido reconocidos dentro del ranking Super empresas de G...

Motorola Solutions
500 W. Monroe Street, Chicago, 60661, US
Last Update: 15/09/2026
About Motorola Solutions | Solving for safer Safety and security are at the heart of everything we do at Motorola Solutions. We build and connect technologies to help protect people, property and places. Our solutions foster the collaboration that’s critical for safer ...
Compliance Ranges Comparison

Prime Communications MX







Motorola Solutions






Benchmark & Cyber Underwriting Signals
Incidents vs Telecommunications Industry Avg (This Year)
Prime Communications MX has 45.05% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for Motorola Solutions in 2026.
Incident History - Prime Communications MX (X = Date, Y = Severity)
Prime Communications MX cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Motorola Solutions (X = Date, Y = Severity)
Motorola Solutions cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Prime Communications MX

Motorola Solutions
FAQ
Latest Global CVEs
HTTP/2 servers could end up crashing due to inadvertently modifying its HPACK encoder concurrently. This happens because the server modifies the HPACK encoder from two goroutines without synchronization: one uses the encoder to encode a HEADERS frame as part of a response sent to a client and the other modifies the encoder's table size when handling a SETTINGS frame containing SETTINGS_HEADER_TABLE_SIZE that a client sends. A malicious client can repeatedly send a request while changing the header table size to crash the server.
Multiple ECH outer extension references are not permitted under RFC 9849; previously, a client could send a well-crafted packet that could trigger memory exhaustion in the server process by specifying multiple references. We now reject these as malformed and curb the memory amplification vector as a result.
A trusted template author may have previously written a valid template wherein the use of the 'yield' keyword would not be correctly escaped. We now ensure that valid keyword uses are escaped and non-keyword uses are not escaped.
Improper certificate validation in Microsoft Partner Center allows an unauthorized attacker to elevate privileges over a network.
Authorization bypass through user-controlled key in Microsoft Bookings allows an unauthorized attacker to elevate privileges over a network.