Comparison Overview
SinoCorrugated

SinoCorrugated
Kompleks MITEC No.8, Jalan Dutamas 2 , Kuala Lumpur, Kuala Lumpur, 50480 , MY
Last Update: 21/02/2026
SinoCorrugated is world's professional trade show for corrugated equipment and consumables, technologies and trends with 21 years of history. SinoCorrugated 2025 in Shanghai is dedicated to establishing an international platform where visitors and buyers see new product...

Tetra Pak
70 Avenue Général-Guisan, CH-1009 PULLY/LAUSANNE, Case Postale 446, CH
Last Update: 01/04/2026
We’re here to make food safe and available. It’s why we provide advanced food production systems, from product creation and recipe testing to processing, filling, packaging, logistics, services and beyond. We support almost every food and beverage category with tailored...
Compliance Ranges Comparison

SinoCorrugated







Tetra Pak






Benchmark & Cyber Underwriting Signals
Incidents vs Packaging and Containers Manufacturing Industry Avg (This Year)
No incidents recorded for SinoCorrugated in 2026.
Incidents vs Packaging and Containers Manufacturing Industry Avg (This Year)
No incidents recorded for Tetra Pak in 2026.
Incident History - SinoCorrugated (X = Date, Y = Severity)
SinoCorrugated cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Tetra Pak (X = Date, Y = Severity)
Tetra Pak cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

SinoCorrugated

Tetra Pak
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.