Comparison Overview

Semiconductor Climate Consortium
N/A
Last Update: 19/03/2026
The SCC is focused on the challenges of climate change and works to speed industry value chain efforts to reduce greenhouse gas emissions in member company operations and in other sectors of our value chain. We believe that the collaboration of our member companies, wit...

Marvell Technology
5488 Marvell Lane, Santa Clara, 95054, US
Last Update: 01/08/2026
We believe that infrastructure powers progress. That execution is as essential as innovation. That better collaboration builds better technology. At Marvell, We go all in with you. Focused and determined, we unite behind your goals as our own. We leverage our unrivaled...
Compliance Ranges Comparison
Semiconductor Climate Consortium







Marvell Technology






Benchmark & Cyber Underwriting Signals
Incidents vs Semiconductor Manufacturing Industry Avg (This Year)
No incidents recorded for Semiconductor Climate Consortium in 2026.
Incidents vs Semiconductor Manufacturing Industry Avg (This Year)
No incidents recorded for Marvell Technology in 2026.
Incident History - Semiconductor Climate Consortium (X = Date, Y = Severity)
Semiconductor Climate Consortium cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Marvell Technology (X = Date, Y = Severity)
Marvell Technology cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Semiconductor Climate Consortium

Marvell Technology
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.