Comparison Overview
LUXSHARE-ICT CO., LTD.

LUXSHARE-ICT CO., LTD.
內湖區民權東路六段15巷12號, 台北市, 114, TW
Last Update: 05/04/2026
Building an Intelligent World of the Internet of Everything Established on May 24, 2004, Luxshare Precision successfully listed on the ChiNext Board of Shenzhen Stock Exchange on September 15, 2010 (stock code: 002475). The Company is committed to providing integrated i...

Apple
1 Apple Park Way, Cupertino, 95014, US
Last Update: 08/08/2026
We’re a diverse collective of thinkers and doers, continually reimagining what’s possible to help us all do what we love in new ways. And the same innovation that goes into our products also applies to our practices — strengthening our commitment to leave the world bett...
Compliance Ranges Comparison

LUXSHARE-ICT CO., LTD.







Apple






Benchmark & Cyber Underwriting Signals
Incidents vs Computers and Electronics Manufacturing Industry Avg (This Year)
LUXSHARE-ICT CO., LTD. has 41.18% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Computers and Electronics Manufacturing Industry Avg (This Year)
Apple has 2400.0% more incidents than the average of all companies with at least one recorded incident.
Incident History - LUXSHARE-ICT CO., LTD. (X = Date, Y = Severity)
LUXSHARE-ICT CO., LTD. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Apple (X = Date, Y = Severity)
Apple cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

LUXSHARE-ICT CO., LTD.

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