Comparison Overview
Ecobank Uganda

Ecobank Uganda
Kafu Rd, Kampala, 8a, UG
Last Update: 31/01/2026
Ecobank is the leading pan-African bank with operations in 33 African countries across the continent, more than any other bank! Ecobank Uganda is a leading commercial bank established in 2009, regulated by the Bank of Uganda. Call us on 0312 354100 email alleug-contactc...

Shriram Finance Limited
Wockhardt Towers, Level-3, West Wing, C-2, G-Block, Bandra-Kurla Complex, Bandra (East), Mumbai, IN, 400051
Last Update: 01/04/2026
Shriram Finance is the country’s biggest retail NBFC offering credit solutions for commercial vehicles, two-wheeler loans, car loans, home loans, gold loans, personal and small business loans. We are part of the 50-year-old Shriram Group, a financial conglomerate that h...
Compliance Ranges Comparison

Ecobank Uganda







Shriram Finance Limited






Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Ecobank Uganda in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Shriram Finance Limited in 2026.
Incident History - Ecobank Uganda (X = Date, Y = Severity)
Ecobank Uganda cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Shriram Finance Limited (X = Date, Y = Severity)
Shriram Finance Limited cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Ecobank Uganda

Shriram Finance Limited
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.