Comparison Overview
Amdocs Labs

Amdocs Labs
N/A
Last Update: 18/03/2026
Amdocs Labs is a hub of innovation for telco businesses, offering a sandbox environment where service providers, enterprises, and partners can incubate new solutions and accelerate commercialization of those services. With deep expertise and collaboration with various p...

Orange
111, Quai du Président Roosevelt, Issy-les-Moulineaux, 92130, FR
Last Update: 15/08/2026
Orange is one of the world’s leading telecommunications operators with revenues of 40.3 billion euros in 2024 and 127,000 employees worldwide at 31 December 2024, including 71,000 employees in France. The Group has a total customer base of 291 million customers worldw...
Compliance Ranges Comparison

Amdocs Labs







Orange






Benchmark & Cyber Underwriting Signals
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for Amdocs Labs in 2026.
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for Orange in 2026.
Incident History - Amdocs Labs (X = Date, Y = Severity)
Amdocs Labs cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Orange (X = Date, Y = Severity)
Orange cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Amdocs Labs

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