CVE-2017-15350 Vulnerability Analysis & Exploit Details

CVE-2017-15350
Vulnerability Scoring

5.3
/10
Significant Risk

Security assessments indicate that CVE-2017-15350 presents a notable risk, potentially requiring prompt mitigation.

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: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2017-15350 Details

Status: Modified

Last updated: 🕒 21 Nov 2024, 03:14 UTC
Originally published on: 🕓 15 Feb 2018, 16:29 UTC

Time between publication and last update: 2470 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

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

CVE-2017-15350 Vulnerability Summary

CVE-2017-15350: The Common Open Policy Service Protocol (COPS) module in Huawei DP300 V500R002C00, IPS Module V100R001C10, V100R001C20, V100R001C30, V500R001C00, V500R001C20, V500R001C30, V500R001C50, NGFW Module V100R001C10, V100R001C20, V100R001C30, V500R001C00, V500R001C20, NIP6300 V500R001C00, V500R001C20, V500R001C30, V500R001C50, NIP6600 V500R001C00, V500R001C20, V500R001C30, V500R001C50, NIP6800 V500R001C50, RP200 V500R002C00, V600R006C00, SVN5600 V200R003C00, V200R003C10, SVN5800 V200R003C00, V200R003C10,SVN5800-C V200R003C00, V200R003C10, Secospace USG6300 V100R001C10, V100R001C20, V100R001C30, V500R001C00, V500R001C20, V500R001C30, V500R001C50, Secospace USG6500 V100R001C10, V100R001C20, V100R001C30, V500R001C00, V500R001C20, V500R001C30, V500R001C50, Secospace USG6600 V100R001C00, V100R001C20, V100R001C30, V500R001C00, V500R001C20, V500R001C30, V500R001C50, TE30 V100R001C02, V100R001C10, V500R002C00, V600R006C00, TE40 V500R002C00, V600R006C00, TE50 V500R002C00, V600R006C00, TE60 V100R001C01, V100R001C10, V500R002C00, V600R006C00, TP3206 V100R002C00, V100R002C10,USG9500 V500R001C00, V500R001C20, V500R001C30, V500R001C50 haa a buffer overflow vulnerability. An unauthenticated, remote attacker could exploit this vulnerability by sending specially crafted message to the affected products. The vulnerability is due to insufficient input validation of the message, which could result in a buffer overflow. Successful exploit may cause some services abnormal.

Assessing the Risk of CVE-2017-15350

Access Complexity Graph

The exploitability of CVE-2017-15350 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-15350

With low attack complexity and no required privileges, CVE-2017-15350 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

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-15350, 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-15350, 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-15350 has no significant impact on data confidentiality.
  • Integrity: None
    CVE-2017-15350 poses no threat to data integrity.
  • Availability: Low
    CVE-2017-15350 may slightly degrade system performance without fully affecting service availability.

Exploit Prediction Scoring System (EPSS)

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

EPSS Score: 0.211% (probability of exploit)

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

CVE-2017-15350 References

External References

CWE Common Weakness Enumeration

CWE-119

CAPEC Common Attack Pattern Enumeration and Classification

  • Buffer Overflow via Environment Variables CAPEC-10 This attack pattern involves causing a buffer overflow through manipulation of environment variables. Once the adversary finds that they can modify an environment variable, they may try to overflow associated buffers. This attack leverages implicit trust often placed in environment variables.
  • Overflow Buffers CAPEC-100 Buffer Overflow attacks target improper or missing bounds checking on buffer operations, typically triggered by input injected by an adversary. As a consequence, an adversary is able to write past the boundaries of allocated buffer regions in memory, causing a program crash or potentially redirection of execution as per the adversaries' choice.
  • Buffer Manipulation CAPEC-123 An adversary manipulates an application's interaction with a buffer in an attempt to read or modify data they shouldn't have access to. Buffer attacks are distinguished in that it is the buffer space itself that is the target of the attack rather than any code responsible for interpreting the content of the buffer. In virtually all buffer attacks the content that is placed in the buffer is immaterial. Instead, most buffer attacks involve retrieving or providing more input than can be stored in the allocated buffer, resulting in the reading or overwriting of other unintended program memory.
  • Client-side Injection-induced Buffer Overflow CAPEC-14 This type of attack exploits a buffer overflow vulnerability in targeted client software through injection of malicious content from a custom-built hostile service. This hostile service is created to deliver the correct content to the client software. For example, if the client-side application is a browser, the service will host a webpage that the browser loads.
  • Filter Failure through Buffer Overflow CAPEC-24 In this attack, the idea is to cause an active filter to fail by causing an oversized transaction. An attacker may try to feed overly long input strings to the program in an attempt to overwhelm the filter (by causing a buffer overflow) and hoping that the filter does not fail securely (i.e. the user input is let into the system unfiltered).
  • MIME Conversion CAPEC-42 An attacker exploits a weakness in the MIME conversion routine to cause a buffer overflow and gain control over the mail server machine. The MIME system is designed to allow various different information formats to be interpreted and sent via e-mail. Attack points exist when data are converted to MIME compatible format and back.
  • Overflow Binary Resource File CAPEC-44 An attack of this type exploits a buffer overflow vulnerability in the handling of binary resources. Binary resources may include music files like MP3, image files like JPEG files, and any other binary file. These attacks may pass unnoticed to the client machine through normal usage of files, such as a browser loading a seemingly innocent JPEG file. This can allow the adversary access to the execution stack and execute arbitrary code in the target process.
  • Buffer Overflow via Symbolic Links CAPEC-45 This type of attack leverages the use of symbolic links to cause buffer overflows. An adversary can try to create or manipulate a symbolic link file such that its contents result in out of bounds data. When the target software processes the symbolic link file, it could potentially overflow internal buffers with insufficient bounds checking.
  • Overflow Variables and Tags CAPEC-46 This type of attack leverages the use of tags or variables from a formatted configuration data to cause buffer overflow. The adversary crafts a malicious HTML page or configuration file that includes oversized strings, thus causing an overflow.
  • Buffer Overflow via Parameter Expansion CAPEC-47 In this attack, the target software is given input that the adversary knows will be modified and expanded in size during processing. This attack relies on the target software failing to anticipate that the expanded data may exceed some internal limit, thereby creating a buffer overflow.
  • Buffer Overflow in an API Call CAPEC-8 This attack targets libraries or shared code modules which are vulnerable to buffer overflow attacks. An adversary who has knowledge of known vulnerable libraries or shared code can easily target software that makes use of these libraries. All clients that make use of the code library thus become vulnerable by association. This has a very broad effect on security across a system, usually affecting more than one software process.
  • Buffer Overflow in Local Command-Line Utilities CAPEC-9 This attack targets command-line utilities available in a number of shells. An adversary can leverage a vulnerability found in a command-line utility to escalate privilege to root.

Vulnerable Configurations

  • cpe:2.3:o:huawei:dp300_firmware:v500r002c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:dp300_firmware:v500r002c00:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:dp300:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:dp300:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ips_module_firmware:v100r001c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ips_module_firmware:v100r001c10:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ips_module_firmware:v100r001c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ips_module_firmware:v100r001c20:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ips_module_firmware:v100r001c30:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ips_module_firmware:v100r001c30:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ips_module_firmware:v500r001c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ips_module_firmware:v500r001c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ips_module_firmware:v500r001c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ips_module_firmware:v500r001c20:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ips_module_firmware:v500r001c30:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ips_module_firmware:v500r001c30:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ips_module_firmware:v500r001c50:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ips_module_firmware:v500r001c50:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:ips_module:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:ips_module:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ngfw_module_firmware:v100r001c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ngfw_module_firmware:v100r001c10:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ngfw_module_firmware:v100r001c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ngfw_module_firmware:v100r001c20:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ngfw_module_firmware:v100r001c30:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ngfw_module_firmware:v100r001c30:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ngfw_module_firmware:v500r001c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ngfw_module_firmware:v500r001c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ngfw_module_firmware:v500r001c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ngfw_module_firmware:v500r001c20:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:ngfw_module:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:ngfw_module:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:nip6300_firmware:v500r001c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:nip6300_firmware:v500r001c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:nip6300_firmware:v500r001c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:nip6300_firmware:v500r001c20:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:nip6300_firmware:v500r001c30:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:nip6300_firmware:v500r001c30:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:nip6300_firmware:v500r001c50:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:nip6300_firmware:v500r001c50:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:nip6300:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:nip6300:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:nip6600_firmware:v500r001c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:nip6600_firmware:v500r001c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:nip6600_firmware:v500r001c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:nip6600_firmware:v500r001c20:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:nip6600_firmware:v500r001c30:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:nip6600_firmware:v500r001c30:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:nip6600_firmware:v500r001c50:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:nip6600_firmware:v500r001c50:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:nip6600:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:nip6600:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:nip6800_firmware:v500r001c50:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:nip6800_firmware:v500r001c50:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:nip6800:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:nip6800:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:svn5800-c_firmware:v200r003c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:svn5800-c_firmware:v200r003c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:svn5800-c_firmware:v200r003c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:svn5800-c_firmware:v200r003c10:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:svn5800-c:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:svn5800-c:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:rp200_firmware:v500r002c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:rp200_firmware:v500r002c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:rp200_firmware:v600r006c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:rp200_firmware:v600r006c00:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:rp200:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:rp200:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:svn5600_firmware:v200r003c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:svn5600_firmware:v200r003c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:svn5600_firmware:v200r003c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:svn5600_firmware:v200r003c10:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:svn5600:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:svn5600:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:svn5800_firmware:v200r003c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:svn5800_firmware:v200r003c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:svn5800_firmware:v200r003c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:svn5800_firmware:v200r003c10:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:svn5800:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:svn5800:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:secospace_usg6300_firmware:v100r001c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:secospace_usg6300_firmware:v100r001c10:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:secospace_usg6300_firmware:v100r001c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:secospace_usg6300_firmware:v100r001c20:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:secospace_usg6300_firmware:v100r001c30:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:secospace_usg6300_firmware:v100r001c30:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:secospace_usg6300_firmware:v500r001c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:secospace_usg6300_firmware:v500r001c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:secospace_usg6300_firmware:v500r001c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:secospace_usg6300_firmware:v500r001c20:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:secospace_usg6300_firmware:v500r001c30:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:secospace_usg6300_firmware:v500r001c30:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:secospace_usg6300_firmware:v500r001c50:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:secospace_usg6300_firmware:v500r001c50:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:secospace_usg6300:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:secospace_usg6300:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:secospace_usg6500_firmware:v100r001c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:secospace_usg6500_firmware:v100r001c10:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:secospace_usg6500_firmware:v100r001c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:secospace_usg6500_firmware:v100r001c20:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:secospace_usg6500_firmware:v100r001c30:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:secospace_usg6500_firmware:v100r001c30:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:secospace_usg6500_firmware:v500r001c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:secospace_usg6500_firmware:v500r001c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:secospace_usg6500_firmware:v500r001c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:secospace_usg6500_firmware:v500r001c20:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:secospace_usg6500_firmware:v500r001c30:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:secospace_usg6500_firmware:v500r001c30:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:secospace_usg6500_firmware:v500r001c50:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:secospace_usg6500_firmware:v500r001c50:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:secospace_usg6500:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:secospace_usg6500:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:secospace_usg6600_firmware:v100r001c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:secospace_usg6600_firmware:v100r001c10:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:secospace_usg6600_firmware:v100r001c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:secospace_usg6600_firmware:v100r001c20:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:secospace_usg6600_firmware:v100r001c30:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:secospace_usg6600_firmware:v100r001c30:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:secospace_usg6600_firmware:v500r001c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:secospace_usg6600_firmware:v500r001c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:secospace_usg6600_firmware:v500r001c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:secospace_usg6600_firmware:v500r001c20:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:secospace_usg6600_firmware:v500r001c30:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:secospace_usg6600_firmware:v500r001c30:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:secospace_usg6600_firmware:v500r001c50:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:secospace_usg6600_firmware:v500r001c50:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:secospace_usg6600:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:secospace_usg6600:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:te30_firmware:v100r001c02:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:te30_firmware:v100r001c02:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:te30_firmware:v100r001c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:te30_firmware:v100r001c10:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:te30_firmware:v500r002c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:te30_firmware:v500r002c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:te30_firmware:v600r006c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:te30_firmware:v600r006c00:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:te30:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:te30:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:te40_firmware:v500r002c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:te40_firmware:v500r002c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:te40_firmware:v600r006c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:te40_firmware:v600r006c00:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:te40:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:te40:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:te50_firmware:v500r002c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:te50_firmware:v500r002c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:te50_firmware:v600r006c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:te50_firmware:v600r006c00:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:te50:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:te50:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:te60_firmware:v100r001c01:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:te60_firmware:v100r001c01:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:te60_firmware:v100r001c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:te60_firmware:v100r001c10:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:te60_firmware:v500r002c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:te60_firmware:v500r002c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:te60_firmware:v600r006c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:te60_firmware:v600r006c00:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:te60:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:te60:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tp3206_firmware:v100r002c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tp3206_firmware:v100r002c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tp3206_firmware:v100r002c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tp3206_firmware:v100r002c10:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:tp3206:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:tp3206:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:usg9500_firmware:v500r001c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:usg9500_firmware:v500r001c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:usg9500_firmware:v500r001c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:usg9500_firmware:v500r001c20:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:usg9500_firmware:v500r001c30:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:usg9500_firmware:v500r001c30:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:usg9500_firmware:v500r001c50:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:usg9500_firmware:v500r001c50:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:usg9500:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:usg9500:-:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2017-15350: 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-3809 – The Debug Log Manager plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the auto-refresh debug log in all versions up to, and i...
  • CVE-2025-2111 – The Insert Headers And Footers plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.1.1. This i...
  • CVE-2024-13926 – The WP-Syntax WordPress plugin through 1.2 does not properly handle input, allowing an attacker to create a post containing a large number of tags,...
  • CVE-2025-3103 – The CLEVER - HTML5 Radio Player With History - Shoutcast and Icecast - Elementor Widget Addon plugin for WordPress is vulnerable to arbitrary file ...
  • CVE-2025-3275 – The Themesflat Addons For Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the TF E Slider widget in all versions up...