CVE-2018-3737 Vulnerability Analysis & Exploit Details

CVE-2018-3737
Vulnerability Scoring

7.5
/10
Very High Risk

Highly exploitable, CVE-2018-3737 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-2018-3737 Details

Status: Modified

Last updated: 🕓 21 Nov 2024, 04:05 UTC
Originally published on: 🕑 07 Jun 2018, 02:29 UTC

Time between publication and last update: 2359 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-2018-3737 Vulnerability Summary

CVE-2018-3737: sshpk is vulnerable to ReDoS when parsing crafted invalid public keys.

Assessing the Risk of CVE-2018-3737

Access Complexity Graph

The exploitability of CVE-2018-3737 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-2018-3737

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

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

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

CVE-2018-3737 References

External References

CWE Common Weakness Enumeration

CWE-185

CAPEC Common Attack Pattern Enumeration and Classification

  • Command Delimiters CAPEC-15 An attack of this type exploits a programs' vulnerabilities that allows an attacker's commands to be concatenated onto a legitimate command with the intent of targeting other resources such as the file system or database. The system that uses a filter or denylist input validation, as opposed to allowlist validation is vulnerable to an attacker who predicts delimiters (or combinations of delimiters) not present in the filter or denylist. As with other injection attacks, the attacker uses the command delimiter payload as an entry point to tunnel through the application and activate additional attacks through SQL queries, shell commands, network scanning, and so on.
  • Argument Injection CAPEC-6 An attacker changes the behavior or state of a targeted application through injecting data or command syntax through the targets use of non-validated and non-filtered arguments of exposed services or methods.
  • Using Slashes in Alternate Encoding CAPEC-79 This attack targets the encoding of the Slash characters. An adversary would try to exploit common filtering problems related to the use of the slashes characters to gain access to resources on the target host. Directory-driven systems, such as file systems and databases, typically use the slash character to indicate traversal between directories or other container components. For murky historical reasons, PCs (and, as a result, Microsoft OSs) choose to use a backslash, whereas the UNIX world typically makes use of the forward slash. The schizophrenic result is that many MS-based systems are required to understand both forms of the slash. This gives the adversary many opportunities to discover and abuse a number of common filtering problems. The goal of this pattern is to discover server software that only applies filters to one version, but not the other.

Vulnerable Configurations

  • cpe:2.3:a:joyent:sshpk:1.0.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:joyent:sshpk:1.0.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:joyent:sshpk:1.0.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:joyent:sshpk:1.0.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:joyent:sshpk:1.0.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:joyent:sshpk:1.0.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:joyent:sshpk:1.0.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:joyent:sshpk:1.0.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:joyent:sshpk:1.0.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:joyent:sshpk:1.0.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:joyent:sshpk:1.1.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:joyent:sshpk:1.1.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:joyent:sshpk:1.2.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:joyent:sshpk:1.2.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:joyent:sshpk:1.2.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:joyent:sshpk:1.2.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:joyent:sshpk:1.3.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:joyent:sshpk:1.3.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:joyent:sshpk:1.4.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:joyent:sshpk:1.4.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:joyent:sshpk:1.4.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:joyent:sshpk:1.4.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:joyent:sshpk:1.4.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:joyent:sshpk:1.4.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:joyent:sshpk:1.4.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:joyent:sshpk:1.4.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:joyent:sshpk:1.4.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:joyent:sshpk:1.4.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:joyent:sshpk:1.4.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:joyent:sshpk:1.4.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:joyent:sshpk:1.4.6:*:*:*:*:node.js:*:*
    cpe:2.3:a:joyent:sshpk:1.4.6:*:*:*:*:node.js:*:*
  • cpe:2.3:a:joyent:sshpk:1.4.7:*:*:*:*:node.js:*:*
    cpe:2.3:a:joyent:sshpk:1.4.7:*:*:*:*:node.js:*:*
  • cpe:2.3:a:joyent:sshpk:1.5.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:joyent:sshpk:1.5.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:joyent:sshpk:1.5.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:joyent:sshpk:1.5.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:joyent:sshpk:1.6.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:joyent:sshpk:1.6.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:joyent:sshpk:1.6.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:joyent:sshpk:1.6.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:joyent:sshpk:1.6.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:joyent:sshpk:1.6.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:joyent:sshpk:1.7.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:joyent:sshpk:1.7.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:joyent:sshpk:1.7.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:joyent:sshpk:1.7.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:joyent:sshpk:1.7.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:joyent:sshpk:1.7.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:joyent:sshpk:1.7.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:joyent:sshpk:1.7.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:joyent:sshpk:1.7.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:joyent:sshpk:1.7.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:joyent:sshpk:1.8.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:joyent:sshpk:1.8.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:joyent:sshpk:1.8.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:joyent:sshpk:1.8.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:joyent:sshpk:1.8.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:joyent:sshpk:1.8.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:joyent:sshpk:1.8.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:joyent:sshpk:1.8.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:joyent:sshpk:1.9.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:joyent:sshpk:1.9.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:joyent:sshpk:1.9.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:joyent:sshpk:1.9.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:joyent:sshpk:1.9.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:joyent:sshpk:1.9.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:joyent:sshpk:1.10.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:joyent:sshpk:1.10.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:joyent:sshpk:1.10.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:joyent:sshpk:1.10.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:joyent:sshpk:1.11.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:joyent:sshpk:1.11.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:joyent:sshpk:1.12.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:joyent:sshpk:1.12.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:joyent:sshpk:1.13.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:joyent:sshpk:1.13.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:joyent:sshpk:1.13.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:joyent:sshpk:1.13.1:*:*:*:*:node.js:*:*

Protect Your Infrastructure against CVE-2018-3737: 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-26205 – Lua 5.4.7, when the debug library is used, has a out-of-bounds read and segmentation violation in mainpositionTV in ltable.c. NOTE: this is dispute...
  • CVE-2025-26204 – Lua 5.4.7, when the debug library is used, has a out-of-bounds read and segmentation violation in equalkey in ltable.c. NOTE: this is disputed beca...
  • CVE-2025-2129 – A vulnerability was found in Mage AI 0.9.75. It has been classified as problematic. This affects an unknown part. The manipulation leads to insecur...
  • CVE-2025-2127 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla. It has been classified as problematic. Affected is an unknown function of th...
  • CVE-2025-2126 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla and classified as critical. This issue affects some unknown processing of the...