Comparison Overview
Devoteam S Team GmbH

Devoteam S Team GmbH
Gutenbergstr. 10, Weiterstadt, Hessen, 64331, DE
Last Update: 03/12/2025
Devoteam S Team ist bei rund 200 Kunden in über 800 Projekten einer der wichtigsten strategischen Partner im SAP Umfeld. Insbesondere wenn es um den modernen SAP Betrieb auf den wichtigsten Hyperscalern, wie GCP, Azure und AWS geht. Unsere SAP Spezialisten stemmen seit ...

Infosys
Infosys Limited, Bangalore, Karnataka, IN, 560100
Last Update: 07/10/2026
Infosys is a global leader in next-generation digital services and consulting. We enable clients in more than 50 countries to navigate their digital transformation. With over three decades of experience in managing the systems and workings of global enterprises, we expe...
Compliance Ranges Comparison

Devoteam S Team GmbH







Infosys






Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Devoteam S Team GmbH in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Infosys in 2026.
Incident History - Devoteam S Team GmbH (X = Date, Y = Severity)
Devoteam S Team GmbH cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Infosys (X = Date, Y = Severity)
Infosys cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Devoteam S Team GmbH

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