Comparison Overview
Dragontail Systems

Dragontail Systems
673 Bourke Street, Melbourne, undefined, undefined, undefined, AU
Last Update: 08/03/2026
Dragontail Systems is a global leading B2B company, that provides a revolutionary software solution to optimize and streamline the food preparation and dispatch, mainly to the QSR (Quick Service Restaurant) industry. We are proud to be part of Yum! Brands, a company w...

Prosus
Gustav Mahlerplein 5, Amsterdam, North Holland, NL, 1082MS
Last Update: 09/08/2026
Prosus is the power behind the world’s leading lifestyle e-commerce brands. Bringing together bold ideas and the power of AI, Prosus builds technology ecosystems where lifestyle ecommerce brands can become global success stories. These ecosystems span three core geogra...
Compliance Ranges Comparison

Dragontail Systems







Prosus






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

Dragontail Systems

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