Comparison Overview
DISH Network Technologies

DISH Network Technologies
SALARPURIA SATTVA EMINENCE, Ground and First Floor # 175/176 ORR , Bengaluru, Karnataka , IN, 560037
Last Update: 17/02/2026
DISH Network Technologies India Pvt. Ltd is a subsidiary of EchoStar Corporation (NASDAQ: SATS) that’s been at the forefront of technology. Since 1980, the organisation has served as a disruptive force, driving innovation and value on behalf of consumers. Our products i...

Globo
Rua Lopes Quintas, 303, Rio de Janeiro, BR
Last Update: 14/09/2026
A globo é feita de gente que quer fazer diferente, fazer junto, fazer o futuro. Gente espalhada por todo o país (e mundo!) trabalhando com conteúdo, notícias, negócios, tecnologia e brasilidade de sobra. Canais na TV aberta e por assinatura, produtos digitais como gl...
Compliance Ranges Comparison

DISH Network Technologies







Globo






Benchmark & Cyber Underwriting Signals
Incidents vs Technology, Information and Media Industry Avg (This Year)
No incidents recorded for DISH Network Technologies in 2026.
Incidents vs Technology, Information and Media Industry Avg (This Year)
No incidents recorded for Globo in 2026.
Incident History - DISH Network Technologies (X = Date, Y = Severity)
DISH Network Technologies cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Globo (X = Date, Y = Severity)
Globo cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

DISH Network Technologies

Globo
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.