Comparison Overview
IEEE DiscoveryPoint for Communications

IEEE DiscoveryPoint for Communications
445 Hoes Lane, Piscataway, 08854, US
Last Update: 12/12/2025
IEEE DiscoveryPoint for Communications is an all-in-one platform built for engineers in industry to design and develop technology solutions. Put your trust in the platform that brings subject-focused information together from hundreds of vetted sources. Quickly find th...

Proximus Group
Boulevard du Roi Albert II 27, Brussels, 1030, BE
Last Update: 14/09/2026
Proximus Group is a provider of future-proof connectivity, IT and digital services, headquartered in Brussels. The Group is actively engaged in building a connected world that people trust, so society blooms. The Domestic segment is focused on providing state-of-the ar...
Compliance Ranges Comparison

IEEE DiscoveryPoint for Communications







Proximus Group






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

IEEE DiscoveryPoint for Communications

Proximus Group
FAQ
Latest Global CVEs
Heym from 0.0.55 before 0.0.121 contains a privilege escalation vulnerability that allows shared collaborators to overwrite a workflow's error_workflow_id because the field is missing from OWNER_ONLY_EXECUTION_FIELDS. Attackers can point the error workflow to their own workflow with an HTTP node, and when the parent workflow errors the owner's decrypted credentials are injected and exfiltrated.
Nodemailer from 3.0.0 before 10.0.10 contains a quadratic complexity denial of service vulnerability in the SMTP client reply parser in SMTPConnection._onData and isPartialResponse. A malicious SMTP server or on-path attacker can stream continuation lines without a completion line before authentication, blocking the Node.js event loop and exhausting memory.
Nodemailer from 3.0.0 before 10.0.10 contains a denial of service vulnerability in MessageParser.parseHeaders that allows users to exhaust CPU through quadratic header unfolding. Attackers can supply large recipient lists or long headers that fold into tens of thousands of continuation lines, blocking the Node.js event loop during DKIM signing.
Nodemailer from 3.0.0 before 10.0.13 contains an improper input validation vulnerability in its address parser that fails to strip RFC 5322 comments inside angle-bracket addresses. Attackers can supply recipients like a display name with a parenthesized comment in the domain, so illegal characters reach envelope.to and RCPT TO, causing rejected delivery or parser interpretation conflicts that bypass domain allow-lists.
Nodemailer 3.0.0 before 10.0.13 has a regular expression denial of service in SMTPConnection._actionEHLO, whose four AUTH mechanism detection regexes contain overlapping whitespace sub-patterns that backtrack quadratically. A malicious or man-in-the-middle SMTP server can reply to EHLO with 250-AUTH, a long whitespace run and a non-matching token, blocking the Node.js event loop for tens of seconds to hours before authentication.