Comparison Overview
ManageEngine LATAM

ManageEngine LATAM
Autopista norte, km 19 Centro Empresarial TYFA, Oficina 202, Chía, Cundinamarca, CO, 250008
Last Update: 04/12/2025
Como la división de administración de TI de Zoho Corporation, ManageEngine se concentra en brindar soluciones flexibles que funcionen para todo tipo de empresas independientemente de su tamaño o presupuesto. #ITSM #ITOM #SIEM #UEMS #Ciberseguridad #Cybersecurity Manage...

IGT
6355 S Buffalo Dr, Las Vegas, NV, US, 89113
Last Update: 15/09/2026
IGT is a leading global provider of gaming, digital and financial technology solutions, formed through the combination of International Game Technology PLC’s Gaming & Digital Business and Everi Holdings Inc. IGT’s offering spans gaming machines, game content and systems...
Compliance Ranges Comparison

ManageEngine LATAM







IGT






Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for ManageEngine LATAM in 2026.
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for IGT in 2026.
Incident History - ManageEngine LATAM (X = Date, Y = Severity)
ManageEngine LATAM cyber incidents detection timeline including parent company and subsidiaries.
Incident History - IGT (X = Date, Y = Severity)
IGT cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

ManageEngine LATAM

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