Comparison Overview
M
M
Redmond, US
Last Update: 24/03/2026
As businesses of all sizes grapple with the same key questions in the wake of COVID-19, the purpose of this community is to bring people together to share what they're learning and how they're managing through change during this time. Ask questions on the topics that ma...
Avaya
350 Mount Kemble Ave, Morristown, 07960, US
Last Update: 01/04/2026
At Avaya, we give our customers the freedom to take their business in the directions that benefit them most. We provide the paths for both customers and their employees where every moment big and small can drive in the moment, memorable experiences. The journey is their...
Compliance Ranges Comparison
M
Avaya
Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for M in 2026.
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for Avaya in 2026.
Incident History - M (X = Date, Y = Severity)
M cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Avaya (X = Date, Y = Severity)
Avaya cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
M
Avaya
FAQ
Latest Global CVEs
Pronetiqs IntraVUE versions 3.2.1a14 and prior have an inadequate encryption strength vulnerability which could allow an attacker to steal admin credentials via weak hash or a pass-the-hash attack.
Pronetiqs IntraVUE versions 3.2.1a14 and prior have an exposure of sensitive system information to an unauthorized control sphere vulnerability which could allow for asset discovery by unauthenticated users.
Pronetiqs IntraVUE versions 3.2.1a14 and prior have an unintended proxy or intermediary vulnerability which could allow an attacker to use an active proxy, which would bypass OT segmentation.
Pronetiqs IntraVUE Versions 3.2.1a14 and prior have a plaintext storage of a password vulnerability that could expose cleartext credentials through the API.
Pronetiqs IntraVUE versions 3.2.1a14 and prior have an exposure of sensitive system information to an unauthorized control sphere vulnerability which could expose the underlying host/share filesystem.