Comparison Overview
BDO Perú

BDO Perú
Av. Camino Real N° 456, San Isidro, undefined, Lima 27, PE
Last Update: 04/12/2025
La red global de BDO se extiende a lo largo de 166 países y territorios, con 115,661 personas trabajando en 1,776 oficinas y todas bajo un mismo objetivo: brindar a nuestros clientes un servicio excepcional. BDO hoy en día, es una Firma de servicios profesionales con 3...

PwC Deutschland
Friedrich-Ebert-Anlage 35-37, Frankfurt am Main, DE, 60327
Last Update: 30/03/2026
PwC is the leading auditing and consulting company in Germany. As an independent member of the international PwC network, it offers its services worldwide. PwC audits and advises leading industrial and service companies of all sizes. In Germany, over 15,000 employees g...
Compliance Ranges Comparison

BDO Perú







PwC Deutschland






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

BDO Perú

PwC Deutschland
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.