Comparison Overview
Applied Materials Japan
Applied Materials Japan
ヨコソーレインボータワー８階, 東京都港区海岸3－20－20 , undefined, 〒108-8444 , JP
Last Update: 09/03/2026
イノベーションでよりよい未来を可能に。アプライド マテリアルズは、材料工学ソリューションのリーディングカンパニーです。原子レベル、産業規模で材料を改質する専門知識をもって、お客様が可能性を現実に変えるお手伝いをします。 アプライド マテリアルズ ジャパンは1979年に設立され、初めてアジアに進出しました。 半導体業界に関する話題で皆さんと交流できることを楽しみにしています。ご意見をお待ちしておりますが、当コミュニティにとって不快な環境となるコメントは削除させていただきます。ご了承ください。
MediaTek
No.1, Dusing Rd. 1, Hsin-Chu, 30078, TW
Last Update: 06/06/2026
MediaTek Incorporated (TWSE: 2454) is a global fabless semiconductor company that enables nearly 2 billion connected devices a year. We are a market leader in developing innovative systems-on-chip (SoC) for mobile, home entertainment, connectivity and IoT products. Our ...
Compliance Ranges Comparison
Applied Materials Japan
MediaTek
Benchmark & Cyber Underwriting Signals
Incidents vs Semiconductor Manufacturing Industry Avg (This Year)
No incidents recorded for Applied Materials Japan in 2026.
Incidents vs Semiconductor Manufacturing Industry Avg (This Year)
MediaTek has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Applied Materials Japan (X = Date, Y = Severity)
Applied Materials Japan cyber incidents detection timeline including parent company and subsidiaries.
Incident History - MediaTek (X = Date, Y = Severity)
MediaTek cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Applied Materials Japan
MediaTek
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.