te60 is a software product offered by huawei. This product is widely deployed in production environments, making vulnerability monitoring essential for organizations relying on it. Security vulnerabilities in products of this category can affect system availability, data confidentiality, and integrity across entire networks. The significant number of reported vulnerabilities indicates this product has received substantial security scrutiny and community focus over time. Regular assessment of known vulnerabilities and timely patching are fundamental components of responsible system administration for any deployment of this software.
SecUtils has identified 83 known vulnerabilities affecting huawei te60. This includes 1 critical-severity issue and 20 high-severity issues that warrant immediate attention. Vulnerabilities in this product have been disclosed spanning from 2015 to 2020, indicating a recent active security attention. 50 medium-severity issues and 12 low-severity issues complete the vulnerability landscape. Organizations should prioritize patching based on deployment context, asset criticality, and exploitation likelihood rather than severity alone.
| ID | Date Published | Last Modified | Severity (CVSSv3) | Severity (CVSSv2) | Exploit Available |
|---|---|---|---|---|---|
| CVE-2015-2808 | 2015-04-01 | 2025-04-12 | - | 5.0 | Likely |
| CVE-2015-8672 | 2016-01-12 | 2025-04-12 | 5.3 | 5.0 | Likely |
| CVE-2015-8673 | 2016-01-12 | 2025-04-12 | 6.8 | 4.6 | Unknown |
| CVE-2017-2722 | 2017-11-22 | 2025-04-20 | 8.8 | 6.5 | Likely |
| CVE-2017-15318 | 2017-12-22 | 2025-04-20 | 7.5 | 7.8 | Likely |
| CVE-2017-15319 | 2017-12-22 | 2025-04-20 | 7.5 | 7.8 | Likely |
| CVE-2017-15320 | 2017-12-22 | 2025-04-20 | 7.5 | 7.8 | Likely |
| CVE-2017-15331 | 2018-02-15 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2017-15332 | 2018-02-15 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2017-15334 | 2018-02-15 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2017-15335 | 2018-02-15 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2017-15336 | 2018-02-15 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2017-15337 | 2018-02-15 | 2024-11-21 | 3.7 | 4.3 | Likely |
| CVE-2017-15338 | 2018-02-15 | 2024-11-21 | 3.7 | 4.3 | Likely |
| CVE-2017-15339 | 2018-02-15 | 2024-11-21 | 3.7 | 4.3 | Likely |
| CVE-2017-15341 | 2018-02-15 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2017-15342 | 2018-02-15 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2017-15350 | 2018-02-15 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2017-15353 | 2018-02-15 | 2024-11-21 | 3.7 | 4.3 | Likely |
| CVE-2017-15354 | 2018-02-15 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2017-15355 | 2018-02-15 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2017-15356 | 2018-02-15 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2017-17151 | 2018-02-15 | 2024-11-21 | 5.9 | 4.3 | Likely |
| CVE-2017-17182 | 2018-02-15 | 2024-11-21 | 4.3 | 4.0 | Likely |
| CVE-2017-17183 | 2018-02-15 | 2024-11-21 | 4.3 | 4.0 | Likely |
| CVE-2017-17184 | 2018-02-15 | 2024-11-21 | 4.3 | 4.0 | Likely |
| CVE-2017-17185 | 2018-02-15 | 2024-11-21 | 4.3 | 4.0 | Likely |
| CVE-2017-17186 | 2018-02-15 | 2024-11-21 | 5.4 | 5.5 | Likely |
| CVE-2017-17187 | 2018-02-15 | 2024-11-21 | 4.3 | 4.0 | Likely |
| CVE-2017-17283 | 2018-02-15 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2017-17284 | 2018-02-15 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2017-17288 | 2018-02-15 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2017-17289 | 2018-02-15 | 2024-11-21 | 3.3 | 2.1 | Unknown |
| CVE-2017-17290 | 2018-02-15 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2017-17291 | 2018-02-15 | 2024-11-21 | 5.5 | 2.1 | Unknown |
| CVE-2017-17292 | 2018-02-15 | 2024-11-21 | 3.3 | 2.1 | Unknown |
| CVE-2017-17293 | 2018-02-15 | 2024-11-21 | 3.3 | 2.1 | Unknown |
| CVE-2017-17294 | 2018-02-15 | 2024-11-21 | 3.3 | 2.1 | Unknown |
| CVE-2017-17298 | 2018-02-15 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2017-17301 | 2018-02-15 | 2024-11-21 | 9.8 | 7.5 | Likely |
| CVE-2017-17302 | 2018-02-15 | 2024-11-21 | 3.3 | 2.1 | Unknown |
| CVE-2017-17131 | 2018-03-05 | 2024-11-21 | 5.7 | 6.3 | Unknown |
| CVE-2017-17134 | 2018-03-05 | 2024-11-21 | 5.5 | 2.1 | Unknown |
| CVE-2017-17135 | 2018-03-05 | 2024-11-21 | 5.5 | 2.1 | Unknown |
| CVE-2017-17136 | 2018-03-05 | 2024-11-21 | 5.5 | 2.1 | Unknown |
| CVE-2017-17137 | 2018-03-05 | 2024-11-21 | 5.5 | 2.1 | Unknown |
| CVE-2017-17138 | 2018-03-05 | 2024-11-21 | 5.5 | 2.1 | Unknown |
| CVE-2017-17142 | 2018-03-05 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2017-17143 | 2018-03-05 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2017-17144 | 2018-03-05 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2017-17150 | 2018-03-09 | 2024-11-21 | 5.5 | 2.1 | Unknown |
| CVE-2017-17199 | 2018-03-09 | 2024-11-21 | 5.9 | 4.3 | Likely |
| CVE-2017-17200 | 2018-03-09 | 2024-11-21 | 5.9 | 4.3 | Likely |
| CVE-2017-17216 | 2018-03-09 | 2024-11-21 | 5.9 | 4.3 | Likely |
| CVE-2017-17217 | 2018-03-09 | 2024-11-21 | 5.9 | 4.3 | Likely |
| CVE-2017-17218 | 2018-03-09 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2017-17219 | 2018-03-09 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2017-17220 | 2018-03-09 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2017-17281 | 2018-03-09 | 2024-11-21 | 4.3 | 4.0 | Likely |
| CVE-2017-17303 | 2018-03-09 | 2024-11-21 | 4.9 | 4.0 | Likely |
| CVE-2017-15314 | 2018-03-09 | 2024-11-21 | 5.5 | 2.1 | Unknown |
| CVE-2017-15323 | 2018-03-09 | 2024-11-21 | 5.5 | 4.9 | Unknown |
| CVE-2017-17282 | 2018-03-09 | 2024-11-21 | 3.1 | 2.9 | Unknown |
| CVE-2017-17308 | 2018-04-11 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2017-17310 | 2018-04-19 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2017-17251 | 2018-04-24 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2017-17252 | 2018-04-24 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2017-17253 | 2018-04-24 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2017-17254 | 2018-04-24 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2017-17255 | 2018-04-24 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2017-17256 | 2018-04-24 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2017-17257 | 2018-04-24 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2017-17258 | 2018-04-24 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2017-17314 | 2018-04-30 | 2024-11-21 | 3.7 | 4.3 | Likely |
| CVE-2017-17315 | 2018-05-24 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2017-17316 | 2018-07-02 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2017-17317 | 2018-07-02 | 2024-11-21 | 3.7 | 4.3 | Likely |
| CVE-2019-19413 | 2020-01-21 | 2024-11-21 | 7.5 | 7.8 | Likely |
| CVE-2019-19414 | 2020-01-21 | 2024-11-21 | 7.5 | 7.8 | Likely |
| CVE-2020-1841 | 2020-02-17 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2019-19415 | 2020-07-08 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2019-19416 | 2020-07-08 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2019-19417 | 2020-07-08 | 2024-11-21 | 7.5 | 5.0 | Likely |
SecUtils normalizes and enriches National Vulnerability Database (NVD) records for huawei te60 by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and structuring the data for rapid analysis and asset correlation. For every vulnerability listed, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference information to enable organizations to prioritize patching and risk assessment efficiently. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for vulnerability management and security operations.