CVE-2020-9099 Vulnerability Analysis & Exploit Details

CVE-2020-9099
Vulnerability Scoring

9.8
/10
Critical Risk

As a catastrophic security flaw, CVE-2020-9099 has severe implications, demanding immediate intervention.

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-2020-9099 Details

Status: Modified

Last updated: 🕠 21 Nov 2024, 05:40 UTC
Originally published on: 🕑 08 Jun 2020, 14:15 UTC

Time between publication and last update: 1626 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:H/I:H/A:H

CVE-2020-9099 Vulnerability Summary

CVE-2020-9099: Huawei products IPS Module; NGFW Module; NIP6300; NIP6600; NIP6800; Secospace USG6300; Secospace USG6500; Secospace USG6600; USG9500 with versions of V500R001C00; V500R001C20; V500R001C30; V500R001C50; V500R001C60; V500R001C80; V500R005C00; V500R005C10; V500R005C20; V500R002C00; V500R002C10; V500R002C20; V500R002C30 have an improper authentication vulnerability. Attackers need to perform some operations to exploit the vulnerability. Successful exploit may obtain certain permissions on the device.

Assessing the Risk of CVE-2020-9099

Access Complexity Graph

The exploitability of CVE-2020-9099 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-2020-9099

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

  • Confidentiality: High
    Exploiting CVE-2020-9099 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2020-9099 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: High
    CVE-2020-9099 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.309% (probability of exploit)

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

CVE-2020-9099 References

External References

CWE Common Weakness Enumeration

CWE-287

CAPEC Common Attack Pattern Enumeration and Classification

  • Authentication Abuse CAPEC-114 An attacker obtains unauthorized access to an application, service or device either through knowledge of the inherent weaknesses of an authentication mechanism, or by exploiting a flaw in the authentication scheme's implementation. In such an attack an authentication mechanism is functioning but a carefully controlled sequence of events causes the mechanism to grant access to the attacker.
  • Authentication Bypass CAPEC-115 An attacker gains access to application, service, or device with the privileges of an authorized or privileged user by evading or circumventing an authentication mechanism. The attacker is therefore able to access protected data without authentication ever having taken place.
  • Identity Spoofing CAPEC-151 Identity Spoofing refers to the action of assuming (i.e., taking on) the identity of some other entity (human or non-human) and then using that identity to accomplish a goal. An adversary may craft messages that appear to come from a different principle or use stolen / spoofed authentication credentials.
  • Fake the Source of Data CAPEC-194 An adversary takes advantage of improper authentication to provide data or services under a falsified identity. The purpose of using the falsified identity may be to prevent traceability of the provided data or to assume the rights granted to another individual. One of the simplest forms of this attack would be the creation of an email message with a modified "From" field in order to appear that the message was sent from someone other than the actual sender. The root of the attack (in this case the email system) fails to properly authenticate the source and this results in the reader incorrectly performing the instructed action. Results of the attack vary depending on the details of the attack, but common results include privilege escalation, obfuscation of other attacks, and data corruption/manipulation.
  • Exploiting Trust in Client CAPEC-22 An attack of this type exploits vulnerabilities in client/server communication channel authentication and data integrity. It leverages the implicit trust a server places in the client, or more importantly, that which the server believes is the client. An attacker executes this type of attack by communicating directly with the server where the server believes it is communicating only with a valid client. There are numerous variations of this type of attack.
  • Utilizing REST's Trust in the System Resource to Obtain Sensitive Data CAPEC-57 This attack utilizes a REST(REpresentational State Transfer)-style applications' trust in the system resources and environment to obtain sensitive data once SSL is terminated.
  • Session Hijacking CAPEC-593 This type of attack involves an adversary that exploits weaknesses in an application's use of sessions in performing authentication. The adversary is able to steal or manipulate an active session and use it to gain unathorized access to the application.
  • Token Impersonation CAPEC-633 An adversary exploits a weakness in authentication to create an access token (or equivalent) that impersonates a different entity, and then associates a process/thread to that that impersonated token. This action causes a downstream user to make a decision or take action that is based on the assumed identity, and not the response that blocks the adversary.
  • Upload a Web Shell to a Web Server CAPEC-650 By exploiting insufficient permissions, it is possible to upload a web shell to a web server in such a way that it can be executed remotely. This shell can have various capabilities, thereby acting as a "gateway" to the underlying web server. The shell might execute at the higher permission level of the web server, providing the ability the execute malicious code at elevated levels.
  • Adversary in the Middle (AiTM) CAPEC-94 An adversary targets the communication between two components (typically client and server), in order to alter or obtain data from transactions. A general approach entails the adversary placing themself within the communication channel between the two components.

Vulnerable Configurations

  • 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:o:huawei:ips_module_firmware:v500r001c60:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ips_module_firmware:v500r001c60:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ips_module_firmware:v500r001c80:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ips_module_firmware:v500r001c80:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ips_module_firmware:v500r005c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ips_module_firmware:v500r005c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ips_module_firmware:v500r005c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ips_module_firmware:v500r005c10:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ips_module_firmware:v500r005c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ips_module_firmware:v500r005c20:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:ips_module:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:ips_module:-:*:*:*:*:*:*:*
  • 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:o:huawei:ngfw_module_firmware:v500r001c30:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ngfw_module_firmware:v500r001c30:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ngfw_module_firmware:v500r001c50:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ngfw_module_firmware:v500r001c50:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ngfw_module_firmware:v500r001c60:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ngfw_module_firmware:v500r001c60:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ngfw_module_firmware:v500r002c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ngfw_module_firmware:v500r002c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ngfw_module_firmware:v500r002c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ngfw_module_firmware:v500r002c10:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ngfw_module_firmware:v500r002c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ngfw_module_firmware:v500r002c20:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ngfw_module_firmware:v500r002c30:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ngfw_module_firmware:v500r002c30:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ngfw_module_firmware:v500r005c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ngfw_module_firmware:v500r005c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ngfw_module_firmware:v500r005c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ngfw_module_firmware:v500r005c10:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ngfw_module_firmware:v500r005c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ngfw_module_firmware:v500r005c20:*:*:*:*:*:*:*
  • 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:o:huawei:nip6300_firmware:v500r001c60:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:nip6300_firmware:v500r001c60:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:nip6300_firmware:v500r001c80:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:nip6300_firmware:v500r001c80:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:nip6300_firmware:v500r005c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:nip6300_firmware:v500r005c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:nip6300_firmware:v500r005c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:nip6300_firmware:v500r005c10:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:nip6300_firmware:v500r005c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:nip6300_firmware:v500r005c20:*:*:*:*:*:*:*
  • 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:o:huawei:nip6600_firmware:v500r001c60:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:nip6600_firmware:v500r001c60:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:nip6600_firmware:v500r001c80:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:nip6600_firmware:v500r001c80:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:nip6600_firmware:v500r005c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:nip6600_firmware:v500r005c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:nip6600_firmware:v500r005c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:nip6600_firmware:v500r005c10:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:nip6600_firmware:v500r005c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:nip6600_firmware:v500r005c20:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:nip6600:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:nip6600:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:nip6800_firmware:v500r001c60:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:nip6800_firmware:v500r001c60:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:nip6800_firmware:v500r001c80:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:nip6800_firmware:v500r001c80:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:nip6800_firmware:v500r005c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:nip6800_firmware:v500r005c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:nip6800_firmware:v500r005c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:nip6800_firmware:v500r005c10:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:nip6800_firmware:v500r005c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:nip6800_firmware:v500r005c20:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:nip6800:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:nip6800:-:*:*:*:*:*:*:*
  • 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:o:huawei:secospace_usg6300_firmware:v500r001c60:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:secospace_usg6300_firmware:v500r001c60:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:secospace_usg6300_firmware:v500r001c80:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:secospace_usg6300_firmware:v500r001c80:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:secospace_usg6300_firmware:v500r005c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:secospace_usg6300_firmware:v500r005c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:secospace_usg6300_firmware:v500r005c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:secospace_usg6300_firmware:v500r005c10:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:secospace_usg6300_firmware:v500r005c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:secospace_usg6300_firmware:v500r005c20:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:secospace_usg6300:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:secospace_usg6300:-:*:*:*:*:*:*:*
  • 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:o:huawei:secospace_usg6500_firmware:v500r001c60:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:secospace_usg6500_firmware:v500r001c60:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:secospace_usg6500_firmware:v500r001c80:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:secospace_usg6500_firmware:v500r001c80:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:secospace_usg6500_firmware:v500r005c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:secospace_usg6500_firmware:v500r005c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:secospace_usg6500_firmware:v500r005c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:secospace_usg6500_firmware:v500r005c10:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:secospace_usg6500_firmware:v500r005c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:secospace_usg6500_firmware:v500r005c20:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:secospace_usg6500:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:secospace_usg6500:-:*:*:*:*:*:*:*
  • 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:o:huawei:secospace_usg6600_firmware:v500r001c60:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:secospace_usg6600_firmware:v500r001c60:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:secospace_usg6600_firmware:v500r001c80:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:secospace_usg6600_firmware:v500r001c80:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:secospace_usg6600_firmware:v500r005c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:secospace_usg6600_firmware:v500r005c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:secospace_usg6600_firmware:v500r005c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:secospace_usg6600_firmware:v500r005c10:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:secospace_usg6600_firmware:v500r005c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:secospace_usg6600_firmware:v500r005c20:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:secospace_usg6600:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:secospace_usg6600:-:*:*:*:*:*:*:*
  • 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:o:huawei:usg9500_firmware:v500r001c60:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:usg9500_firmware:v500r001c60:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:usg9500_firmware:v500r001c80:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:usg9500_firmware:v500r001c80:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:usg9500_firmware:v500r005c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:usg9500_firmware:v500r005c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:usg9500_firmware:v500r005c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:usg9500_firmware:v500r005c10:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:usg9500_firmware:v500r005c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:usg9500_firmware:v500r005c20:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:usg9500:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:usg9500:-:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2020-9099: 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-3284 – The User Registration & Membership – Custom Registration Form, Login Form, and User Profile plugin for WordPress is vulnerable to Cross-Site Reques...
  • CVE-2025-3278 – The UrbanGo Membership plugin for WordPress is vulnerable to privilege escalation in versions up to, and including, 1.0.4. This is due to the plugi...
  • CVE-2025-2010 – The JobWP – Job Board, Job Listing, Career Page and Recruitment Plugin plugin for WordPress is vulnerable to SQL Injection via the 'jobwp_upload_re...
  • CVE-2025-43903 – NSSCryptoSignBackend.cc in Poppler before 25.04.0 does not verify the adbe.pkcs7.sha1 signatures on documents, resulting in potential signature forgeries.
  • CVE-2025-3796 – A vulnerability classified as critical has been found in PHPGurukul Men Salon Management System 1.0. This affects an unknown part of the file /admi...