Comparison Overview
LG유플러스 (LG Uplus)
LG유플러스 (LG Uplus)
32, Hangang-daero, Yongsan-gu, 04389, KR
Last Update: 05/10/2026
Simply. U+
Huawei
Huawei Technologies Co., Ltd., Shenzhen, 518129, CN
Last Update: 06/09/2026
Huawei is a leading global provider of information and communications technology (ICT) infrastructure and smart devices. With integrated solutions across four key domains – telecom networks, IT, smart devices, and cloud services – we are committed to bringing digital to...
Compliance Ranges Comparison
LG유플러스 (LG Uplus)
Huawei
Benchmark & Cyber Underwriting Signals
Incidents vs Telecommunications Industry Avg (This Year)
LG유플러스 (LG Uplus) has 45.95% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Telecommunications Industry Avg (This Year)
Huawei has 0.99% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - LG유플러스 (LG Uplus) (X = Date, Y = Severity)
LG유플러스 (LG Uplus) cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Huawei (X = Date, Y = Severity)
Huawei cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
LG유플러스 (LG Uplus)
Huawei
FAQ
Latest Global CVEs
IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 could allow a remote authenticated attacker to obtain sensitive information due to exposure of session tokens in the HTML response.
IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 could allow a remote authenticated attacker to obtain sensitive information due to an XML external entity (XXE) injection flaw.
IBM Aspera Enterprise WebApps 1.0.0 through 1.0.6 could allow a local attacker to obtain sensitive information due to cleartext transmission of sensitive information.
IBM Planning Analytics 2.0, and 2.1 could allow a remote authenticated attacker to execute arbitrary code due to a stack-based buffer overflow.
IBM DataStage on Cloud Pak for Data 5.4.0.0 can allow a man-in-the-middle attacker to present a forged TLS certificate, intercept the connection, and capture the IAM bearer Authorization header automatically attached by the session adapter. The captured token grants full platform-scope tenant API access, enabling the attacker to read and manipulate the victim's DataStage projects, flows, assets, and pipeline definitions. This is client-side SDK code running on the user's own machine, so exploitation requires an external network interceptor rather than a co-tenant in the shared cluster.