Comparison Overview
British Chamber of Commerce Vietnam

British Chamber of Commerce Vietnam
25 Le Duan, District 1, Ho Chi Minh City, Ho Chi Minh City, VN, 700000
Last Update: 23/03/2026
The British Chamber Of Commerce Vietnam (“BritCham Vietnam”), started as a luncheon club in 1991, was first licensed in 1998. We were the first ever Foreign Business Group to obtain formal recognition in Vietnam. The BritCham Vietnam now boasts more than 450 members. We...

Intertek
33 Cavendish Square, London, W1G 0PS, GB
Last Update: 01/04/2026
Intertek is a leading Total Quality Assurance provider to industries worldwide. Our network of more than 1,000 laboratories and offices in more than 100 countries, delivers innovative and bespoke Assurance, Testing, Inspection and Certification solutions for our custom...
Compliance Ranges Comparison

British Chamber of Commerce Vietnam







Intertek






Benchmark & Cyber Underwriting Signals
Incidents vs International Trade and Development Industry Avg (This Year)
No incidents recorded for British Chamber of Commerce Vietnam in 2026.
Incidents vs International Trade and Development Industry Avg (This Year)
No incidents recorded for Intertek in 2026.
Incident History - British Chamber of Commerce Vietnam (X = Date, Y = Severity)
British Chamber of Commerce Vietnam cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Intertek (X = Date, Y = Severity)
Intertek cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

British Chamber of Commerce Vietnam

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