CVE-2019-5259 Vulnerability Analysis & Exploit Details

CVE-2019-5259
Vulnerability Scoring

6.5
/10
High Risk

If left unpatched, CVE-2019-5259 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-2019-5259 Details

Status: Modified

Last updated: 🕟 21 Nov 2024, 04:44 UTC
Originally published on: 🕙 16 Dec 2019, 22:15 UTC

Time between publication and last update: 1801 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

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

CVE-2019-5259 Vulnerability Summary

CVE-2019-5259: There is an information leakage vulnerability on some Huawei products(AR120-S;AR1200;AR1200-S;AR150;AR150-S;AR160;AR200;AR200-S;AR2200;AR2200-S;AR3200;AR3600). An attacker with low permissions can view some high-privilege information by running specific commands.Successful exploit could cause an information disclosure condition.

Assessing the Risk of CVE-2019-5259

Access Complexity Graph

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

CVE-2019-5259 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-2019-5259, 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-5259, 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-5259 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: None
    CVE-2019-5259 poses no threat to data integrity.
  • Availability: None
    CVE-2019-5259 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.065% (probability of exploit)

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

CVE-2019-5259 References

External References

CWE Common Weakness Enumeration

CWE-269

CAPEC Common Attack Pattern Enumeration and Classification

  • Privilege Abuse CAPEC-122 An adversary is able to exploit features of the target that should be reserved for privileged users or administrators but are exposed to use by lower or non-privileged accounts. Access to sensitive information and functionality must be controlled to ensure that only authorized users are able to access these resources.
  • Privilege Escalation CAPEC-233 An adversary exploits a weakness enabling them to elevate their privilege and perform an action that they are not supposed to be authorized to perform.
  • Restful Privilege Elevation CAPEC-58 An adversary identifies a Rest HTTP (Get, Put, Delete) style permission method allowing them to perform various malicious actions upon server data due to lack of access control mechanisms implemented within the application service accepting HTTP messages.

Vulnerable Configurations

  • cpe:2.3:o:huawei:ar120-s_firmware:v200r005c32:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar120-s_firmware:v200r005c32:*:*:*:*:*:*:*
  • 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:v200r008c50:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar120-s_firmware:v200r008c50:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar120-s_firmware:v200r009c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar120-s_firmware:v200r009c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar120-s_firmware:v200r010c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar120-s_firmware:v200r010c00:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:ar120-s:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:ar120-s:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar1200_firmware:v200r005c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar1200_firmware:v200r005c20:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar1200_firmware:v200r005c32:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar1200_firmware:v200r005c32:*:*:*:*:*:*:*
  • 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:v200r008c50:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar1200_firmware:v200r008c50:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar1200_firmware:v200r009c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar1200_firmware:v200r009c00:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:ar1200:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:ar1200:-:*:*:*:*:*:*:*
  • 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:v200r005c32:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar1200-s_firmware:v200r005c32:*:*:*:*:*:*:*
  • 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:v200r008c50:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar1200-s_firmware:v200r008c50:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar1200-s_firmware:v200r009c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar1200-s_firmware:v200r009c00:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:ar1200-s:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:ar1200-s:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar150_firmware:v200r005c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar150_firmware:v200r005c20:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar150_firmware:v200r005c32:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar150_firmware:v200r005c32:*:*:*:*:*:*:*
  • 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:v200r008c50:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar150_firmware:v200r008c50:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar150_firmware:v200r009c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar150_firmware:v200r009c00:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:ar150:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:ar150:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar150-s_firmware:v200r005c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar150-s_firmware:v200r005c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar150-s_firmware:v200r005c32:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar150-s_firmware:v200r005c32:*:*:*:*:*:*:*
  • 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:v200r008c50:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar150-s_firmware:v200r008c50:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar150-s_firmware:v200r009c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar150-s_firmware:v200r009c00:*:*:*:*:*:*:*
  • 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:v200r005c32:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar160_firmware:v200r005c32:*:*:*:*:*:*:*
  • 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:v200r008c50:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar160_firmware:v200r008c50:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar160_firmware:v200r009c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar160_firmware:v200r009c00:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:ar160:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:ar160:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar200_firmware:v200r005c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar200_firmware:v200r005c20:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar200_firmware:v200r005c32:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar200_firmware:v200r005c32:*:*:*:*:*:*:*
  • 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:v200r008c50:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar200_firmware:v200r008c50:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar200_firmware:v200r009c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar200_firmware:v200r009c00:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:ar200:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:ar200:-:*:*:*:*:*:*:*
  • 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:v200r005c32:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar200-s_firmware:v200r005c32:*:*:*:*:*:*:*
  • 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:v200r008c50:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar200-s_firmware:v200r008c50:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar200-s_firmware:v200r009c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar200-s_firmware:v200r009c00:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:ar200-s:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:ar200-s:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar2200_firmware:v200r005c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar2200_firmware:v200r005c20:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar2200_firmware:v200r005c32:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar2200_firmware:v200r005c32:*:*:*:*:*:*:*
  • 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:v200r008c50:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar2200_firmware:v200r008c50:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar2200_firmware:v200r009c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar2200_firmware:v200r009c00:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:ar2200:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:ar2200:-:*:*:*:*:*:*:*
  • 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:v200r005c32:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar2200-s_firmware:v200r005c32:*:*:*:*:*:*:*
  • 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:v200r008c50:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar2200-s_firmware:v200r008c50:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar2200-s_firmware:v200r009c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar2200-s_firmware:v200r009c00:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:ar2200-s:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:ar2200-s:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar3200_firmware:v200r005c20:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar3200_firmware:v200r005c20:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar3200_firmware:v200r005c32:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar3200_firmware:v200r005c32:*:*:*:*:*:*:*
  • 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:v200r008c50:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar3200_firmware:v200r008c50:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar3200_firmware:v200r009c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar3200_firmware:v200r009c00:*:*:*:*:*:*:*
  • 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:v200r008c50:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar3600_firmware:v200r008c50:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:ar3600_firmware:v200r009c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:ar3600_firmware:v200r009c00:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:ar3600:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:ar3600:-:*:*:*:*:*:*:*

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