CVE-2019-5304 Vulnerability Analysis & Exploit Details

CVE-2019-5304
Vulnerability Scoring

7.5
/10
Very High Risk

Highly exploitable, CVE-2019-5304 poses a critical security risk that could lead to severe breaches.

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-2019-5304 Details

Status: Modified

Last updated: 🕟 21 Nov 2024, 04:44 UTC
Originally published on: 🕒 03 Jan 2020, 15:15 UTC

Time between publication and last update: 1783 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

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

CVE-2019-5304 Vulnerability Summary

CVE-2019-5304: Some Huawei products have a buffer error vulnerability. An unauthenticated, remote attacker could send specific MPLS Echo Request messages to the target products. Due to insufficient input validation of some parameters in the messages, successful exploit may cause the device to reset.

Assessing the Risk of CVE-2019-5304

Access Complexity Graph

The exploitability of CVE-2019-5304 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-2019-5304

With low attack complexity and no required privileges, CVE-2019-5304 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-2019-5304, 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-2019-5304, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: None
    CVE-2019-5304 has no significant impact on data confidentiality.
  • Integrity: None
    CVE-2019-5304 poses no threat to data integrity.
  • Availability: High
    CVE-2019-5304 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.179% (probability of exploit)

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

CVE-2019-5304 References

External References

CWE Common Weakness Enumeration

CWE-120

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.
  • 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.
  • String Format Overflow in syslog() CAPEC-67 This attack targets applications and software that uses the syslog() function insecurely. If an application does not explicitely use a format string parameter in a call to syslog(), user input can be placed in the format string parameter leading to a format string injection attack. Adversaries can then inject malicious format string commands into the function call leading to a buffer overflow. There are many reported software vulnerabilities with the root cause being a misuse of the syslog() function.
  • 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.
  • Forced Integer Overflow CAPEC-92 This attack forces an integer variable to go out of range. The integer variable is often used as an offset such as size of memory allocation or similarly. The attacker would typically control the value of such variable and try to get it out of range. For instance the integer in question is incremented past the maximum possible value, it may wrap to become a very small, or negative number, therefore providing a very incorrect value which can lead to unexpected behavior. At worst the attacker can execute arbitrary code.

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:v200r008c50:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar120-s_firmware:v200r008c50:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:ar120-s:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:ar120-s:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar1200_firmware:v200r003c01:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar1200_firmware:v200r003c01:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar1200_firmware:v200r005c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar1200_firmware:v200r005c20:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar1200_firmware:v200r006c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar1200_firmware:v200r006c10:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar1200_firmware:v200r007c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar1200_firmware:v200r007c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar1200_firmware:v200r008c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar1200_firmware:v200r008c20:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar1200_firmware:v200r008c50:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar1200_firmware:v200r008c50:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:ar1200:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:ar1200:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar1200-s_firmware:v200r003c01:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar1200-s_firmware:v200r003c01:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar1200-s_firmware:v200r005c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar1200-s_firmware:v200r005c20:*:*:*:*:*:*:*
  • 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:v200r008c50:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar1200-s_firmware:v200r008c50:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:ar1200-s:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:ar1200-s:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar150_firmware:v200r003c01:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar150_firmware:v200r003c01:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar150_firmware:v200r005c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar150_firmware:v200r005c20:*:*:*:*:*:*:*
  • 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:v200r008c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar150_firmware:v200r008c20:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar150_firmware:v200r008c50:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar150_firmware:v200r008c50:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:ar150:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:ar150:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar150-s_firmware:v200r003c01:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar150-s_firmware:v200r003c01:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar150-s_firmware:v200r005c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar150-s_firmware:v200r005c20:*:*:*:*:*:*:*
  • 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:v200r008c50:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar150-s_firmware:v200r008c50:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:ar150-s:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:ar150-s:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar160_firmware:v200r005c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar160_firmware:v200r005c20:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar160_firmware:v200r006c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar160_firmware:v200r006c10:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar160_firmware:v200r007c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar160_firmware:v200r007c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar160_firmware:v200r008c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar160_firmware:v200r008c20:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar160_firmware:v200r008c50:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar160_firmware:v200r008c50:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:ar160:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:ar160:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar200_firmware:v200r003c01:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar200_firmware:v200r003c01:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar200_firmware:v200r005c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar200_firmware:v200r005c20:*:*:*:*:*:*:*
  • 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:v200r008c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar200_firmware:v200r008c20:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar200_firmware:v200r008c50:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar200_firmware:v200r008c50:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:ar200:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:ar200:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar200-s_firmware:v200r003c01:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar200-s_firmware:v200r003c01:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar200-s_firmware:v200r005c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar200-s_firmware:v200r005c20:*:*:*:*:*:*:*
  • 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:v200r008c50:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar200-s_firmware:v200r008c50:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:ar200-s:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:ar200-s:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar2200_firmware:v200r003c01:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar2200_firmware:v200r003c01:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar2200_firmware:v200r005c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar2200_firmware:v200r005c20:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar2200_firmware:v200r006c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar2200_firmware:v200r006c10:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar2200_firmware:v200r007c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar2200_firmware:v200r007c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar2200_firmware:v200r008c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar2200_firmware:v200r008c20:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar2200_firmware:v200r008c50:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar2200_firmware:v200r008c50:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:ar2200:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:ar2200:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar2200-s_firmware:v200r003c01:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar2200-s_firmware:v200r003c01:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar2200-s_firmware:v200r005c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar2200-s_firmware:v200r005c20:*:*:*:*:*:*:*
  • 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:v200r008c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar2200-s_firmware:v200r008c20:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar2200-s_firmware:v200r008c50:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar2200-s_firmware:v200r008c50:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:ar2200-s:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:ar2200-s:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar3200_firmware:v200r003c01:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar3200_firmware:v200r003c01:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar3200_firmware:v200r005c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar3200_firmware:v200r005c20:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar3200_firmware:v200r006c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar3200_firmware:v200r006c10:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar3200_firmware:v200r007c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar3200_firmware:v200r007c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar3200_firmware:v200r008c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar3200_firmware:v200r008c20:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar3200_firmware:v200r008c50:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar3200_firmware:v200r008c50:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:ar3200:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:ar3200:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar3600_firmware:v200r006c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar3600_firmware:v200r006c10:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar3600_firmware:v200r007c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar3600_firmware:v200r007c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar3600_firmware:v200r008c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar3600_firmware:v200r008c20:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar3600_firmware:v200r008c50:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar3600_firmware:v200r008c50:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:ar3600:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:ar3600:-:*:*:*:*:*:*:*
  • 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:h:huawei:ips_module:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:ips_module:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ngfw_module_firmware:v500r001c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ngfw_module_firmware:v500r001c20:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ngfw_module_firmware:v500r002c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ngfw_module_firmware:v500r002c00:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:ngfw_module:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:ngfw_module:-:*:*:*:*:*:*:*
  • 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:h:huawei:nip6300:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:nip6300:-:*:*:*:*:*:*:*
  • 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:h:huawei:nip6600:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:nip6600:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:netengine16ex_firmware:v200r005c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:netengine16ex_firmware:v200r005c20:*:*:*:*:*:*:*
  • 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:v200r008c50:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:netengine16ex_firmware:v200r008c50:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:netengine16ex:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:netengine16ex:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s5700_firmware:v200r005c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s5700_firmware:v200r005c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s5700_firmware:v200r005c02:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s5700_firmware:v200r005c02:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s5700_firmware:v200r005c03:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s5700_firmware:v200r005c03:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s5700_firmware:v200r006c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s5700_firmware:v200r006c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s5700_firmware:v200r007c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s5700_firmware:v200r007c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s5700_firmware:v200r008c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s5700_firmware:v200r008c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s5700_firmware:v200r010c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s5700_firmware:v200r010c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s5700_firmware:v200r011c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s5700_firmware:v200r011c00:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:s5700:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:s5700:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s6700_firmware:v200r005c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s6700_firmware:v200r005c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s6700_firmware:v200r005c01:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s6700_firmware:v200r005c01:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s6700_firmware:v200r005c02:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s6700_firmware:v200r005c02:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s6700_firmware:v200r008c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s6700_firmware:v200r008c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s6700_firmware:v200r010c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s6700_firmware:v200r010c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s6700_firmware:v200r011c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s6700_firmware:v200r011c00:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:s6700:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:s6700:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:srg1300_firmware:v200r003c01:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:srg1300_firmware:v200r003c01:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:srg1300_firmware:v200r005c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:srg1300_firmware:v200r005c20:*:*:*:*:*:*:*
  • 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:v200r008c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:srg1300_firmware:v200r008c20:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:srg1300_firmware:v200r008c50:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:srg1300_firmware:v200r008c50:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:srg1300:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:srg1300:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:srg2300_firmware:v200r003c01:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:srg2300_firmware:v200r003c01:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:srg2300_firmware:v200r005c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:srg2300_firmware:v200r005c20:*:*:*:*:*:*:*
  • 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:v200r008c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:srg2300_firmware:v200r008c20:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:srg2300_firmware:v200r008c50:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:srg2300_firmware:v200r008c50:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:srg2300:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:srg2300:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:srg3300_firmware:v200r003c01:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:srg3300_firmware:v200r003c01:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:srg3300_firmware:v200r005c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:srg3300_firmware:v200r005c20:*:*:*:*:*:*:*
  • 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:v200r008c50:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:srg3300_firmware:v200r008c50:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:srg3300:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:srg3300:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:secospace_antiddos8000_firmware:v500r001c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:secospace_antiddos8000_firmware:v500r001c20:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:secospace_antiddos8000_firmware:v500r001c60:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:secospace_antiddos8000_firmware:v500r001c60:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:secospace_antiddos8000_firmware:v500r005c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:secospace_antiddos8000_firmware:v500r005c00:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:secospace_antiddos8000:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:secospace_antiddos8000:-:*:*:*:*:*:*:*
  • 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:h:huawei:secospace_usg6300:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:secospace_usg6300:-:*:*:*:*:*:*:*
  • 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:h:huawei:secospace_usg6500:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:secospace_usg6500:-:*:*:*:*:*:*:*
  • 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:h:huawei:secospace_usg6600:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:secospace_usg6600:-:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2019-5304: 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...