Comparison Overview
Ogilvy Group Germany

Ogilvy Group Germany
Darmstädter Landstraße 112, Frankfurt, Hessen, 60598, DE
Last Update: 28/04/2026
Die 𝗢𝗴𝗶𝗹𝘃𝘆 𝗚𝗿𝗼𝘂𝗽 𝗚𝗲𝗿𝗺𝗮𝗻𝘆 ist eine der erfolgreichsten Agenturgruppen Deutschlands. Als Creative Company mit Büros in Berlin, Düsseldorf, Frankfurt und Hamburg liefern wir disziplinübergreifende Lösungen für eine zunehmend komplexere Welt. Mit unserem e...

Clinic
20-24 Broadwick St, London, W1F 8HT, GB
Last Update: 14/09/2026
Clinic is an independent creative agency. We create bold ideas, and craft them beautifully, to get people thinking, believing and doing. All of our experience goes into what we do today, and although our world’s constantly changing, the endpoint is still people a...
Compliance Ranges Comparison

Ogilvy Group Germany







Clinic






Benchmark & Cyber Underwriting Signals
Incidents vs Advertising Services Industry Avg (This Year)
No incidents recorded for Ogilvy Group Germany in 2026.
Incidents vs Advertising Services Industry Avg (This Year)
No incidents recorded for Clinic in 2026.
Incident History - Ogilvy Group Germany (X = Date, Y = Severity)
Ogilvy Group Germany cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Clinic (X = Date, Y = Severity)
Clinic cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Ogilvy Group Germany

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