Comparison Overview
Infosys Application Modernization

Infosys Application Modernization
N/A
Last Update: 25/02/2026
The rapidly growing AI economy is blurring the lines between traditional industries, leading to the emergence of innovative business models and new products and services powered by AI. Embracing AI is now crucial for enterprises globally to leverage the numerous opportu...

Orange Business
La Plaine Saint Denis, Paris, FR, 93457 Cedex
Last Update: 04/04/2026
At Orange Business, our ambition is to become the leading european Network and Digital Integrator by leveraging our proven expertise in next-generation connectivity solutions, the cloud and cybersecurity. Our 30,000 women and men are present in 65 countries, where ever...
Compliance Ranges Comparison

Infosys Application Modernization







Orange Business






Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Infosys Application Modernization in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Orange Business in 2026.
Incident History - Infosys Application Modernization (X = Date, Y = Severity)
Infosys Application Modernization cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Orange Business (X = Date, Y = Severity)
Orange Business cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Infosys Application Modernization

Orange Business
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.