CVE-2019-5438 Vulnerability Analysis & Exploit Details

CVE-2019-5438
Vulnerability Scoring

5.3
/10
Significant Risk

Security assessments indicate that CVE-2019-5438 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-2019-5438 Details

Status: Modified

Last updated: 🕟 21 Nov 2024, 04:44 UTC
Originally published on: 🕙 10 May 2019, 22:29 UTC

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

CVE-2019-5438 Vulnerability Summary

CVE-2019-5438: Path traversal using symlink in npm harp module versions <= 0.29.0.

Assessing the Risk of CVE-2019-5438

Access Complexity Graph

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

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

  • Confidentiality: Low
    CVE-2019-5438 could lead to minor leaks of non-critical information without major privacy breaches.
  • Integrity: None
    CVE-2019-5438 poses no threat to data integrity.
  • Availability: None
    CVE-2019-5438 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.159% (probability of exploit)

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

CVE-2019-5438 References

External References

CWE Common Weakness Enumeration

CWE-59

CAPEC Common Attack Pattern Enumeration and Classification

  • Symlink Attack CAPEC-132 An adversary positions a symbolic link in such a manner that the targeted user or application accesses the link's endpoint, assuming that it is accessing a file with the link's name.
  • Using Malicious Files CAPEC-17 An attack of this type exploits a system's configuration that allows an adversary to either directly access an executable file, for example through shell access; or in a possible worst case allows an adversary to upload a file and then execute it. Web servers, ftp servers, and message oriented middleware systems which have many integration points are particularly vulnerable, because both the programmers and the administrators must be in synch regarding the interfaces and the correct privileges for each interface.
  • Leverage Executable Code in Non-Executable Files CAPEC-35 An attack of this type exploits a system's trust in configuration and resource files. When the executable loads the resource (such as an image file or configuration file) the attacker has modified the file to either execute malicious code directly or manipulate the target process (e.g. application server) to execute based on the malicious configuration parameters. Since systems are increasingly interrelated mashing up resources from local and remote sources the possibility of this attack occurring is high.
  • Manipulating Web Input to File System Calls CAPEC-76 An attacker manipulates inputs to the target software which the target software passes to file system calls in the OS. The goal is to gain access to, and perhaps modify, areas of the file system that the target software did not intend to be accessible.

Vulnerable Configurations

  • cpe:2.3:a:harpjs:harp:0.1.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.1.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.2.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.2.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.2.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.2.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.2.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.2.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.2.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.2.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.2.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.2.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.2.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.2.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.2.6:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.2.6:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.3.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.3.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.3.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.3.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.3.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.3.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.3.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.3.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.3.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.3.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.3.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.3.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.3.6:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.3.6:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.4.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.4.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.4.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.4.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.4.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.4.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.4.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.4.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.4.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.4.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.4.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.4.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.5.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.5.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.5.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.5.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.5.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.5.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.5.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.5.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.5.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.5.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.5.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.5.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.5.6:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.5.6:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.6.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.6.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.6.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.6.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.6.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.6.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.7.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.7.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.7.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.7.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.7.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.7.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.7.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.7.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.7.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.7.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.7.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.7.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.7.6:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.7.6:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.7.7:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.7.7:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.7.8:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.7.8:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.7.9:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.7.9:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.7.10:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.7.10:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.8.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.8.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.8.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.8.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.8.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.8.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.8.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.8.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.8.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.8.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.8.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.8.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.8.6:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.8.6:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.8.7:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.8.7:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.8.8:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.8.8:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.8.9:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.8.9:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.8.10:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.8.10:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.8.11:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.8.11:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.8.12:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.8.12:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.8.13:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.8.13:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.9.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.9.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.9.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.9.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.9.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.9.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.9.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.9.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.9.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.9.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.9.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.9.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.10.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.10.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.10.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.10.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.10.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.10.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.11.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.11.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.11.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.11.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.11.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.11.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.12.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.12.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.12.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.12.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.13.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.13.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.14.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.14.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.15.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.15.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.15.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.15.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.15.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.15.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.16.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.16.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.17.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.17.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.18.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.18.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.19.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.19.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.20.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.20.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.20.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.20.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.20.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.20.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.20.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.20.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.21.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.21.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.22.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.22.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.23.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.23.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.24.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.24.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.24.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.24.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.25.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.25.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.26.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.26.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.27.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.27.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.28.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.28.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.28.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.28.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:harpjs:harp:0.29.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:harpjs:harp:0.29.0:*:*:*:*:node.js:*:*

Protect Your Infrastructure against CVE-2019-5438: 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-2024-43107 – Improper Certificate Validation (CWE-295) in the Gallagher Milestone Integration Plugin (MIP) permits unauthenticated messages (e.g. alarm events) ...
  • CVE-2024-41724 – Improper Certificate Validation (CWE-295) in the Gallagher Command Centre SALTO integration allowed an attacker to spoof the SALTO server. Thi...
  • CVE-2025-2133 – A vulnerability classified as problematic was found in ftcms 2.1. Affected by this vulnerability is an unknown functionality of the file /admin/ind...
  • CVE-2025-2132 – A vulnerability classified as critical has been found in ftcms 2.1. Affected is an unknown function of the file /admin/index.php/web/ajax_all_lists...
  • CVE-2025-2131 – A vulnerability was found in dayrui XunRuiCMS up to 4.6.3. It has been rated as problematic. This issue affects some unknown processing of the comp...