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

NVIDIA
2701 San Tomas Expressway, Santa Clara, 95050, US
Last Update: 02/08/2026
Since its founding in 1993, NVIDIA (NASDAQ: NVDA) has been a pioneer in accelerated computing. The company’s invention of the GPU in 1999 sparked the growth of the PC gaming market, redefined computer graphics, ignited the era of modern AI and is fueling the creation of...
Compliance Ranges Comparison

Ingrasys 鴻佰科技股份有限公司







NVIDIA






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)
NVIDIA has 870.87% 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 - NVIDIA (X = Date, Y = Severity)
NVIDIA cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Ingrasys 鴻佰科技股份有限公司

NVIDIA
FAQ
Latest Global CVEs
In OpenStack Designate before 22.0.2, the mDNS handler performs pool-blind lookups when resolving record queries and NOTIFY requests. When two zones with the same name exist across different pools, the lookup fails with a deterministic error, causing the handler to return REFUSED for all DNS queries through that path. The _handle_notify path is exploitable via a single unauthenticated UDP packet. This is independently reachable through the cross-tenant zone overlap described in a different recent CVE, and also affects legitimate same-tenant cross-pool configurations. BIND9 views do not mitigate this issue as mDNS is a shared service upstream of any view configuration.
In OpenStack Designate before 22.0.1, zone creation checks (_is_subzone, _is_superzone, and the duplicate-zone DB constraint) are scoped to the target pool only. An authenticated user can bypass these checks by scheduling a zone to a different pool via the AttributeFilter scheduler, creating an overlapping zone that conflicts with another tenant's zone. This enables cross-tenant DNS hijack (redirecting traffic to attacker-controlled IPs) and DNS denial of service (NODATA responses). Exploitation requires a multi-pool deployment with AttributeFilter enabled in scheduler_filters, which is a non-default but documented and supported configuration for self-service tiering.
UpSnap is a wake on lan web app. Versions prior to 5.4.0 have an OS command injection vulnerability in the UpSnap’s device management functionality due to the presence of unsafe shell command template interpolation using the ip and the mac fields. User-controlled values can be inserted into the wake_cmd and shutdown_cmd templates and executed via /bin/sh -c (Linux) or cmd /C (Windows) without sanitization, resulting in an authenticated Remote Code Execution (RCE). A low-privileged user with permission to create or edit devices can execute arbitrary operating system commands on the UpSnap hosted server. Version 5.4.0 patches the issue.
FUXA is a web-based Process Visualization (SCADA/HMI/Dashboard) software. When `secureEnabled=true`, FUXA `1.3.0-2773` still allows guest and invalid-token requests to read project, alarms, and scheduler APIs. Version 1.3.1 fixes this issue.
FUXA is a web-based Process Visualization (SCADA/HMI/Dashboard) software. In fuxa-server version 1.3.0, the GET /api/project endpoint exposes sensitive project configuration data to guest-context requests even when secureEnabled is enabled. Version 1.3.1 fixes the issue.