CVE-2017-8163 Vulnerability Analysis & Exploit Details

CVE-2017-8163
Vulnerability Scoring

6.5
/10
High Risk

If left unpatched, CVE-2017-8163 could lead to major system disruptions or data loss.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: Low
    Some privileges are necessary to exploit the vulnerability.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2017-8163 Details

Status: Modified

Last updated: 🕞 21 Nov 2024, 03:33 UTC
Originally published on: 🕖 22 Nov 2017, 19:29 UTC

Time between publication and last update: 2555 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

CVE-2017-8163 Vulnerability Summary

CVE-2017-8163: AR120-S with software V200R006C10, V200R007C00, V200R008C20, V200R008C30,AR1200 with software V200R006C10, V200R006C13, V200R007C00, V200R007C01, V200R007C02, V200R008C20, V200R008C30,AR1200-S with software V200R006C10, V200R007C00, V200R008C20, V200R008C30,AR150 with software V200R006C10, V200R007C00, V200R007C01, V200R007C02, V200R008C20, V200R008C30,AR150-S with software V200R006C10, V200R007C00, V200R008C20, V200R008C30,AR160 with software V200R006C10, V200R006C12, V200R007C00, V200R007C01, V200R007C02, V200R008C20, V200R008C30,AR200 with software V200R006C10, V200R007C00, V200R007C01, V200R008C20, V200R008C30,AR200-S with software V200R006C10, V200R007C00, V200R008C20, V200R008C30,AR2200 with software V200R006C10, V200R006C13, V200R006C16PWE, V200R007C00, V200R007C01, V200R007C02, V200R008C20, V200R008C30,AR2200-S with software V200R006C10, V200R007C00, V200R008C20, V200R008C30,AR3200 with software V200R006C10, V200R006C11, V200R007C00, V200R007C01, V200R007C02, V200R008C00, V200R008C10, V200R008C20, V200R008C30,AR510 with software V200R006C10, V200R006C12, V200R006C13, V200R006C15, V200R006C16, V200R006C17, V200R007C00, V200R008C20, V200R008C30,NetEngine16EX with software V200R006C10, V200R007C00, V200R008C20, V200R008C30,SMC2.0 with software V100R003C10, V100R005C00, V500R002C00, V600R006C00,SRG1300 with software V200R006C10, V200R007C00, V200R007C02, V200R008C20, V200R008C30,SRG2300 with software V200R006C10, V200R007C00, V200R007C02, V200R008C20, V200R008C30,SRG3300 with software V200R006C10, V200R007C00, V200R008C20, V200R008C30 have an out-of-bounds read vulnerability. Due to insufficient input validation, an authenticated, remote attacker could send specially crafted message to the target device.Successful exploit of the vulnerability could cause out-of-bounds read and system crash.

Assessing the Risk of CVE-2017-8163

Access Complexity Graph

The exploitability of CVE-2017-8163 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2017-8163

CVE-2017-8163 presents an accessible attack vector with minimal effort required. Restricting access controls and implementing security updates are critical to reducing exploitation risks.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2017-8163, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2017-8163, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: None
    CVE-2017-8163 has no significant impact on data confidentiality.
  • Integrity: None
    CVE-2017-8163 poses no threat to data integrity.
  • Availability: High
    CVE-2017-8163 can disrupt system operations, potentially causing complete denial of service (DoS).

Exploit Prediction Scoring System (EPSS)

The EPSS score estimates the probability that this vulnerability will be exploited in the near future.

EPSS Score: 0.121% (probability of exploit)

EPSS Percentile: 47.95% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 52.05% of others.

CVE-2017-8163 References

External References

CWE Common Weakness Enumeration

CWE-125

CAPEC Common Attack Pattern Enumeration and Classification

  • Overread Buffers CAPEC-540 An adversary attacks a target by providing input that causes an application to read beyond the boundary of a defined buffer. This typically occurs when a value influencing where to start or stop reading is set to reflect positions outside of the valid memory location of the buffer. This type of attack may result in exposure of sensitive information, a system crash, or arbitrary code execution.

Vulnerable Configurations

  • cpe:2.3:o:huawei:ar120-s_firmware:v200r006c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar120-s_firmware:v200r006c10:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar120-s_firmware:v200r007c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar120-s_firmware:v200r007c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar120-s_firmware:v200r008c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar120-s_firmware:v200r008c20:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar120-s_firmware:v200r008c30:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar120-s_firmware:v200r008c30:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:ar120-s:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:ar120-s:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar1200_firmware:v200r006c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar1200_firmware:v200r006c10:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar1200_firmware:v200r006c13:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar1200_firmware:v200r006c13:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar1200_firmware:v200r007c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar1200_firmware:v200r007c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar1200_firmware:v200r007c01:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar1200_firmware:v200r007c01:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar1200_firmware:v200r007c02:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar1200_firmware:v200r007c02:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar1200_firmware:v200r008c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar1200_firmware:v200r008c20:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar1200_firmware:v200r008c30:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar1200_firmware:v200r008c30:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:ar1200:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:ar1200:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar1200-s_firmware:v200r006c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar1200-s_firmware:v200r006c10:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar1200-s_firmware:v200r007c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar1200-s_firmware:v200r007c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar1200-s_firmware:v200r008c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar1200-s_firmware:v200r008c20:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar1200-s_firmware:v200r008c30:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar1200-s_firmware:v200r008c30:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:ar1200-s:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:ar1200-s:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar150_firmware:v200r006c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar150_firmware:v200r006c10:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar150_firmware:v200r007c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar150_firmware:v200r007c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar150_firmware:v200r007c01:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar150_firmware:v200r007c01:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar150_firmware:v200r007c02:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar150_firmware:v200r007c02:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar150_firmware:v200r008c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar150_firmware:v200r008c20:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar150_firmware:v200r008c30:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar150_firmware:v200r008c30:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:ar150:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:ar150:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar150-s_firmware:v200r006c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar150-s_firmware:v200r006c10:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar150-s_firmware:v200r007c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar150-s_firmware:v200r007c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar150-s_firmware:v200r008c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar150-s_firmware:v200r008c20:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar150-s_firmware:v200r008c30:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar150-s_firmware:v200r008c30:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:ar150-s:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:ar150-s:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar160_firmware:v200r006c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar160_firmware:v200r006c10:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar160_firmware:v200r006c12:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar160_firmware:v200r006c12:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar160_firmware:v200r007c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar160_firmware:v200r007c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar160_firmware:v200r007c01:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar160_firmware:v200r007c01:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar160_firmware:v200r007c02:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar160_firmware:v200r007c02:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar160_firmware:v200r008c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar160_firmware:v200r008c20:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar160_firmware:v200r008c30:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar160_firmware:v200r008c30:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:ar160:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:ar160:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar200_firmware:v200r006c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar200_firmware:v200r006c10:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar200_firmware:v200r007c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar200_firmware:v200r007c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar200_firmware:v200r007c01:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar200_firmware:v200r007c01:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar200_firmware:v200r008c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar200_firmware:v200r008c20:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar200_firmware:v200r008c30:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar200_firmware:v200r008c30:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:ar200:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:ar200:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar200-s_firmware:v200r006c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar200-s_firmware:v200r006c10:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar200-s_firmware:v200r007c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar200-s_firmware:v200r007c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar200-s_firmware:v200r008c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar200-s_firmware:v200r008c20:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar200-s_firmware:v200r008c30:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar200-s_firmware:v200r008c30:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:ar200-s:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:ar200-s:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar2200_firmware:v200r006c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar2200_firmware:v200r006c10:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar2200_firmware:v200r006c13:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar2200_firmware:v200r006c13:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar2200_firmware:v200r006c16pwe:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar2200_firmware:v200r006c16pwe:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar2200_firmware:v200r007c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar2200_firmware:v200r007c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar2200_firmware:v200r007c01:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar2200_firmware:v200r007c01:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar2200_firmware:v200r007c02:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar2200_firmware:v200r007c02:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar2200_firmware:v200r008c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar2200_firmware:v200r008c20:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar2200_firmware:v200r008c30:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar2200_firmware:v200r008c30:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:ar2200:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:ar2200:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar2200-s_firmware:v200r006c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar2200-s_firmware:v200r006c10:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar2200-s_firmware:v200r007c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar2200-s_firmware:v200r007c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar2200-s_firmware:v200r008c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar2200-s_firmware:v200r008c20:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar2200-s_firmware:v200r008c30:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar2200-s_firmware:v200r008c30:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:ar2200-s:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:ar2200-s:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar3200_firmware:v200r006c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar3200_firmware:v200r006c10:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar3200_firmware:v200r006c11:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar3200_firmware:v200r006c11:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar3200_firmware:v200r007c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar3200_firmware:v200r007c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar3200_firmware:v200r007c01:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar3200_firmware:v200r007c01:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar3200_firmware:v200r007c02:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar3200_firmware:v200r007c02:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar3200_firmware:v200r008c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar3200_firmware:v200r008c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar3200_firmware:v200r008c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar3200_firmware:v200r008c10:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar3200_firmware:v200r008c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar3200_firmware:v200r008c20:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar3200_firmware:v200r008c30:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar3200_firmware:v200r008c30:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:ar3200:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:ar3200:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar510_firmware:v200r006c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar510_firmware:v200r006c10:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar510_firmware:v200r006c12:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar510_firmware:v200r006c12:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar510_firmware:v200r006c13:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar510_firmware:v200r006c13:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar510_firmware:v200r006c15:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar510_firmware:v200r006c15:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar510_firmware:v200r006c16:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar510_firmware:v200r006c16:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar510_firmware:v200r006c17:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar510_firmware:v200r006c17:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar510_firmware:v200r007c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar510_firmware:v200r007c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar510_firmware:v200r008c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar510_firmware:v200r008c20:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar510_firmware:v200r008c30:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar510_firmware:v200r008c30:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:ar510:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:ar510:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:netengine16ex_firmware:v200r006c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:netengine16ex_firmware:v200r006c10:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:netengine16ex_firmware:v200r007c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:netengine16ex_firmware:v200r007c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:netengine16ex_firmware:v200r008c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:netengine16ex_firmware:v200r008c20:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:netengine16ex_firmware:v200r008c30:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:netengine16ex_firmware:v200r008c30:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:netengine16ex:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:netengine16ex:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:smc2.0_firmware:v100r003c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:smc2.0_firmware:v100r003c10:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:smc2.0_firmware:v100r005c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:smc2.0_firmware:v100r005c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:smc2.0_firmware:v500r002c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:smc2.0_firmware:v500r002c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:smc2.0_firmware:v600r006c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:smc2.0_firmware:v600r006c00:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:smc2.0:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:smc2.0:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:srg1300_firmware:v200r006c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:srg1300_firmware:v200r006c10:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:srg1300_firmware:v200r007c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:srg1300_firmware:v200r007c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:srg1300_firmware:v200r007c02:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:srg1300_firmware:v200r007c02:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:srg1300_firmware:v200r008c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:srg1300_firmware:v200r008c20:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:srg1300_firmware:v200r008c30:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:srg1300_firmware:v200r008c30:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:srg1300:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:srg1300:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:srg2300_firmware:v200r006c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:srg2300_firmware:v200r006c10:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:srg2300_firmware:v200r007c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:srg2300_firmware:v200r007c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:srg2300_firmware:v200r007c02:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:srg2300_firmware:v200r007c02:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:srg2300_firmware:v200r008c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:srg2300_firmware:v200r008c20:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:srg2300_firmware:v200r008c30:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:srg2300_firmware:v200r008c30:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:srg2300:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:srg2300:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:srg3300_firmware:v200r006c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:srg3300_firmware:v200r006c10:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:srg3300_firmware:v200r007c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:srg3300_firmware:v200r007c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:srg3300_firmware:v200r008c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:srg3300_firmware:v200r008c20:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:srg3300_firmware:v200r008c30:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:srg3300_firmware:v200r008c30:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:srg3300:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:srg3300:-:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2017-8163: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2025-2130 – A vulnerability was found in OpenXE up to 1.12. It has been declared as problematic. This vulnerability affects unknown code of the component Ticke...
  • CVE-2025-26205 – Lua 5.4.7, when the debug library is used, has a out-of-bounds read and segmentation violation in mainpositionTV in ltable.c. NOTE: this is dispute...
  • CVE-2025-26204 – Lua 5.4.7, when the debug library is used, has a out-of-bounds read and segmentation violation in equalkey in ltable.c. NOTE: this is disputed beca...
  • CVE-2025-2129 – A vulnerability was found in Mage AI 0.9.75. It has been classified as problematic. This affects an unknown part. The manipulation leads to insecur...
  • CVE-2025-2127 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla. It has been classified as problematic. Affected is an unknown function of th...