Comparison Overview
UNIQA Raiffeisen Software Service Kft.

UNIQA Raiffeisen Software Service Kft.
Kossuth L.u.7-9. , Budapest, Magyarország, HU, 1053
Last Update: 04/04/2026
Die UNIQA Raiffeisen Software Service Kft. der verlässliche ungarische IT-Partner im Finanzdienstleistungsbereich für die österreichische UNIQA- und Raiffeisen-Gruppe. Unser Unternehmen wurde im Jahr 1996 unter dem Namen „Syntegra Kft.“, gegründet. Seit 2010 firmiert d...

Persistent Systems
Bhageerath, 402 E, Senapati Bapat Road, Pune, Maharashtra, IN, 411016
Last Update: 02/04/2026
We are an AI-led, platform-driven Digital Engineering and Enterprise Modernization partner, combining deep technical expertise and industry experience to help our clients anticipate what’s next. Our offerings and proven solutions create a unique competitive advantage fo...
Compliance Ranges Comparison

UNIQA Raiffeisen Software Service Kft.







Persistent Systems






Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for UNIQA Raiffeisen Software Service Kft. in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Persistent Systems in 2026.
Incident History - UNIQA Raiffeisen Software Service Kft. (X = Date, Y = Severity)
UNIQA Raiffeisen Software Service Kft. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Persistent Systems (X = Date, Y = Severity)
Persistent Systems cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

UNIQA Raiffeisen Software Service Kft.

Persistent Systems
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.