Comparison Overview
DDB Romania

DDB Romania
Praga, 3, BUCURESTI, București, 011801, RO
Last Update: 02/12/2025
We are part of Omnicom international network and proud members of thegroup - the largest group of communication companies in Romania. Mission Ideas are the fuel of DDB. Creativity Is The Most Powerful Force In Business. And our inspiration? People. Insight ...

Havas
29/30 Quai de Dion Bouton, Puteaux, FR, 92800
Last Update: 04/04/2026
Founded in 1835 in Paris, Havas is one of the world’s largest global communications groups, with nearly 23,000 people in over 100 countries. With the ambition to help brands unlock Growth, Powered by Desire, Havas brings together creativity, media, technology and produc...
Compliance Ranges Comparison

DDB Romania







Havas






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

DDB Romania

Havas
FAQ
Latest Global CVEs
In OpenStack Ironic before 38.0.1, the autodetect deploy interface may fail to run cleaning immediately after enrollment with, or changing to, the autodetect deploy interface.
A flaw was found in Red Hat Quay. A user with FEATURE_BUILD_SUPPORT enabled and repository write access can exploit a Server-Side Request Forgery (SSRF) vulnerability within the build API. This allows the user to provide a malicious URL, causing the Quay builder to make requests to internal network addresses. Such an action could lead to the disclosure of sensitive internal information.
A flaw was found in Red Hat Quay's exported logs feature. An unauthenticated attacker with a valid file ID could download exported action logs without proper authorization. While file IDs are complex, they can be intercepted from plaintext email or webhook callbacks. This vulnerability leads to information disclosure, potentially exposing sensitive data such as usernames, email addresses, IP addresses, and action-specific metadata.
A flaw was found in Red Hat Quay's Stripe billing webhook handler. This vulnerability allows an unauthenticated attacker to forge billing events by sending crafted JSON requests to the `/webhooks/stripe` endpoint without validating the Stripe-Signature header. Successful exploitation can lead to the unauthorized resetting of a namespace's build quota to its maximum and trigger unsolicited billing emails to namespace administrators.
A flaw was found in Red Hat Quay. When the SECURITY_SCANNER_V4_PSK (pre-shared key) is not set, a remote unauthenticated attacker can send POST requests to the security scanner notification endpoint. This allows the attacker to flood the notification queue and inject path traversal characters into Clair API URL paths. The primary consequence is worker resource exhaustion and blind path manipulation on the configured Clair host, potentially leading to a denial of service.