CVE-2019-19397 Vulnerability Analysis & Exploit Details

CVE-2019-19397
Vulnerability Scoring

7.5
/10
Very High Risk

Highly exploitable, CVE-2019-19397 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-19397 Details

Status: Modified

Last updated: 🕟 21 Nov 2024, 04:34 UTC
Originally published on: 🕒 13 Dec 2019, 15:15 UTC

Time between publication and last update: 1804 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:N/A:N

CVE-2019-19397 Vulnerability Summary

CVE-2019-19397: There is a weak algorithm vulnerability in some Huawei products. The affected products use weak algorithms by default. Attackers may exploit the vulnerability to cause information leaks.

Assessing the Risk of CVE-2019-19397

Access Complexity Graph

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

With low attack complexity and no required privileges, CVE-2019-19397 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-19397, 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-19397, 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-2019-19397 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: None
    CVE-2019-19397 poses no threat to data integrity.
  • Availability: None
    CVE-2019-19397 does not impact system 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.168% (probability of exploit)

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

CVE-2019-19397 References

External References

CWE Common Weakness Enumeration

NVD-CWE-noinfo

Vulnerable Configurations

  • cpe:2.3:o:huawei:s12700_firmware:v200r007c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s12700_firmware:v200r007c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s12700_firmware:v200r007c01:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s12700_firmware:v200r007c01:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s12700_firmware:v200r007c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s12700_firmware:v200r007c20:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s12700_firmware:v200r008c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s12700_firmware:v200r008c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s12700_firmware:v200r010c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s12700_firmware:v200r010c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s12700_firmware:v200r011c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s12700_firmware:v200r011c10:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s12700_firmware:v200r012c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s12700_firmware:v200r012c00:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:s12700:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:s12700:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s1700_firmware:v200r006c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s1700_firmware:v200r006c10:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s1700_firmware:v200r010c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s1700_firmware:v200r010c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s1700_firmware:v200r011c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s1700_firmware:v200r011c10:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s1700_firmware:v200r012c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s1700_firmware:v200r012c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s1700_firmware:v200r012c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s1700_firmware:v200r012c20:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:s1700:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:s1700:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s2700_firmware:v200r006c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s2700_firmware:v200r006c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s2700_firmware:v200r006c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s2700_firmware:v200r006c10:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s2700_firmware:v200r007c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s2700_firmware:v200r007c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s2700_firmware:v200r008c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s2700_firmware:v200r008c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s2700_firmware:v200r010c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s2700_firmware:v200r010c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s2700_firmware:v200r011c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s2700_firmware:v200r011c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s2700_firmware:v200r011c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s2700_firmware:v200r011c10:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s2700_firmware:v200r012c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s2700_firmware:v200r012c00:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:s2700:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:s2700:-:*:*:*:*:*:*:*
  • 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:o:huawei:s5700_firmware:v200r011c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s5700_firmware:v200r011c10:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s5700_firmware:v200r012c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s5700_firmware:v200r012c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s5700_firmware:v200r012c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s5700_firmware:v200r012c20:*:*:*:*:*:*:*
  • 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:o:huawei:s6700_firmware:v200r011c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s6700_firmware:v200r011c10:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s6700_firmware:v200r012c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s6700_firmware:v200r012c00:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:s6700:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:s6700:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s7700_firmware:v200r006c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s7700_firmware:v200r006c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s7700_firmware:v200r007c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s7700_firmware:v200r007c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s7700_firmware:v200r008c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s7700_firmware:v200r008c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s7700_firmware:v200r010c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s7700_firmware:v200r010c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s7700_firmware:v200r011c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s7700_firmware:v200r011c10:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s7700_firmware:v200r012c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s7700_firmware:v200r012c00:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:s7700:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:s7700:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s9700_firmware:v200r006c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s9700_firmware:v200r006c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s9700_firmware:v200r007c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s9700_firmware:v200r007c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s9700_firmware:v200r007c01:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s9700_firmware:v200r007c01:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s9700_firmware:v200r008c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s9700_firmware:v200r008c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s9700_firmware:v200r010c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s9700_firmware:v200r010c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s9700_firmware:v200r011c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s9700_firmware:v200r011c10:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s9700_firmware:v200r012c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s9700_firmware:v200r012c00:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:s9700:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:s9700:-:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2019-19397: 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-47424 – Retool (self-hosted) before 3.196.0 allows Host header injection. When the BASE_DOMAIN environment variable is not set, the HTTP host header can be...
  • CVE-2025-3794 – The WPForms – Easy Form Builder for WordPress – Contact Forms, Payment Forms, Surveys, & More plugin for WordPress is vulnerable to Stored Cross-Si...
  • CVE-2025-4494 – A vulnerability, which was classified as critical, was found in JAdmin-JAVA JAdmin 1.0. Affected is the function toLogin of the file NoNeedLoginCon...
  • CVE-2025-4492 – A vulnerability, which was classified as critical, has been found in Campcodes Online Food Ordering System 1.0. This issue affects some unknown pro...
  • CVE-2025-4491 – A vulnerability classified as critical was found in Campcodes Online Food Ordering System 1.0. This vulnerability affects unknown code of the file ...