Comparison Overview
ADB Anticorruption and Integrity

ADB Anticorruption and Integrity
6 ADB Avenue, Mandaluyong, 1550, PH
Last Update: 27/12/2025
Underpinned by ADB's zero tolerance for corruption, the Office of Anticorruption and Integrity aligns with ADB’s commitment to strengthen governance across Asia and the Pacific as it mitigates integrity risks, investigates integrity violations, and promotes integrity am...

John Swire & Sons (H.K.) Ltd.
Hong Kong, HK
Last Update: 01/04/2026
Swire is a highly diversified global business group which has been in operation for over 200 years. It employs over 121,000 people across the world. Swire Group’s businesses span Property, Beverages & Food Chain, Aviation, Marine Services, Trading & Industrial, as well ...
Compliance Ranges Comparison

ADB Anticorruption and Integrity







John Swire & Sons (H.K.) Ltd.






Benchmark & Cyber Underwriting Signals
Incidents vs International Trade and Development Industry Avg (This Year)
No incidents recorded for ADB Anticorruption and Integrity in 2026.
Incidents vs International Trade and Development Industry Avg (This Year)
No incidents recorded for John Swire & Sons (H.K.) Ltd. in 2026.
Incident History - ADB Anticorruption and Integrity (X = Date, Y = Severity)
ADB Anticorruption and Integrity cyber incidents detection timeline including parent company and subsidiaries.
Incident History - John Swire & Sons (H.K.) Ltd. (X = Date, Y = Severity)
John Swire & Sons (H.K.) Ltd. cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

ADB Anticorruption and Integrity

John Swire & Sons (H.K.) Ltd.
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.