Comparison Overview
PT Lion Super Indo

PT Lion Super Indo
Jl. Jendral Gatot Soebroto Kav. 71 - 73, Pancoran, Jakarta, 12870, ID
Last Update: 28/03/2026
Sejak tahun 1997, Super Indo telah bertumbuh dan berkembang di Indonesia melalui kemitraan bersama Ahold Delhaize yang berasal dari Belanda dan Salim Group dari Indonesia. Didukung lebih dari 10,000 karyawan* yang terlatih, Super Indo berhasil menyediakan berbagai macam...

Clicks Group
Cnr. Searle and Pontac Streets, Woodstock, Cape Town, ZA, 8000
Last Update: 01/04/2026
As a leader in the healthcare market, Clicks Group is committed to increasing access to affordable primary healthcare for all South Africans through its Clicks Retail pharmacy, pharmaceutical wholesale and distribution businesses. Founded nearly 58 years ago in 1968, C...
Compliance Ranges Comparison

PT Lion Super Indo







Clicks Group






Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for PT Lion Super Indo in 2026.
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Clicks Group in 2026.
Incident History - PT Lion Super Indo (X = Date, Y = Severity)
PT Lion Super Indo cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Clicks Group (X = Date, Y = Severity)
Clicks Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

PT Lion Super Indo

Clicks Group
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.