Comparison Overview
Ingrasys 鴻佰科技股份有限公司

Ingrasys 鴻佰科技股份有限公司
桃園市蘆竹區南青路1188號, 桃園市, 33066, TW
Last Update: 01/04/2026
鴻佰科技股份有限公司(Ingrasys Inc.)是富士康科技集團(Foxconn Technology Group)的子公司,是世界級智慧型雲網服務產品之技術領導者,提供廣泛的產品和服務,包括伺服器、儲存裝置、高性能計算加速器和創新的環境友善解決方案,協助全球客戶滿足使用需求。公司已獲得AS9100認證,確保提供高品質的航太產品和服務。更多資訊,請參考鴻佰科技相關網站: -> Ingrasys Inc.:https://www.ingrasys.com/ -> LinkedIn:https://www.linkedin.com/c...

ASUS
No.15, Lide Road, Taipei City, 112, TW
Last Update: 15/09/2026
ASUS is a global technology leader delivering incredible experiences that enhance the lives of people everywhere. World renowned for continuously reimagining today’s technologies for tomorrow, ASUS puts users first In Search of Incredible to provide the world’s most inn...
Compliance Ranges Comparison

Ingrasys 鴻佰科技股份有限公司







ASUS






Benchmark & Cyber Underwriting Signals
Incidents vs Computer Hardware Manufacturing Industry Avg (This Year)
No incidents recorded for Ingrasys 鴻佰科技股份有限公司 in 2026.
Incidents vs Computer Hardware Manufacturing Industry Avg (This Year)
ASUS has 390.2% more incidents than the average of all companies with at least one recorded incident.
Incident History - Ingrasys 鴻佰科技股份有限公司 (X = Date, Y = Severity)
Ingrasys 鴻佰科技股份有限公司 cyber incidents detection timeline including parent company and subsidiaries.
Incident History - ASUS (X = Date, Y = Severity)
ASUS cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Ingrasys 鴻佰科技股份有限公司

ASUS
FAQ
Latest Global CVEs
A vulnerability was determined in xuxueli xxl-job up to 3.5.0. The impacted element is an unknown function of the file /jobgroup/insert. This manipulation of the argument Name causes cross site scripting. The attack can be initiated remotely. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way.
A vulnerability was found in Moore Threads MTT S80 Driver Package 340.150. The affected element is the function sub_140006F0C in the library mtdispkm64.sys of the component IOCTL Handler. The manipulation results in improper privilege management. Attacking locally is a requirement. The vendor was contacted early about this disclosure but did not respond in any way.
vLLM Mooncake connector through 0.29.0 fails to properly manage GPU KV cache block ownership when concurrent child requests share a single transfer ID in prefill/decode disaggregated deployments. Attackers can trigger GPU memory exhaustion by submitting completion requests with multiple prompts, causing orphaned KV cache blocks to accumulate until process restart and eventually preventing legitimate requests from executing.
- https://github.com/vllm-project/vllm
- https://github.com/vllm-project/vllm/blob/v0.29.0/vllm/distributed/kv_transfer/kv_connector/v1/mooncake/mooncake_connector.py#L1978-L1989
- https://github.com/vllm-project/vllm/pull/49796
- https://www.vulncheck.com/advisories/vllm-through-0.29.0-gpu-kv-cache-leak-via-mooncake-transfer-id-collision
vLLM through 0.29.0 fails to validate the tp_size parameter in kv_transfer_params on OpenAI-compatible completion endpoints, allowing attackers to allocate unbounded memory. Attackers can supply arbitrary tp_size values in prefill/decode disaggregated deployments to exhaust memory and trigger kernel OOM-kill of the decode worker process.
- https://github.com/vllm-project/vllm
- https://github.com/vllm-project/vllm/blob/v0.29.0/vllm/distributed/kv_transfer/kv_connector/utils.py#L569-L573
- https://github.com/vllm-project/vllm/blob/v0.29.0/vllm/distributed/kv_transfer/kv_connector/v1/nixl/metadata.py#L277
- https://github.com/vllm-project/vllm/pull/51137
- https://www.vulncheck.com/advisories/vllm-through-0.29.0-memory-exhaustion-via-unvalidated-nixl-tp-size
vLLM through 0.29.0 contains a resource exhaustion vulnerability in MooncakeConnector where rejected prefill requests create ownerless transfer placeholders that are never reclaimed. Attackers can send rejected requests to exhaust sender task pools, causing valid requests to be delayed by up to 480 seconds while health checks continue returning success.
- https://github.com/vllm-project/vllm
- https://github.com/vllm-project/vllm/blob/v0.29.0/vllm/distributed/kv_transfer/kv_connector/v1/mooncake/mooncake_connector.py#L1234-L1242
- https://github.com/vllm-project/vllm/pull/51236
- https://www.vulncheck.com/advisories/vllm-through-0.29.0-resource-exhaustion-via-ownerless-mooncake-transfer-placeholders