CVE-2018-25110 Vulnerability Analysis & Exploit Details

CVE-2018-25110
Vulnerability Scoring

7.5
/10
Very High Risk

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

Status: Analyzed

Last updated: 🕞 13 Aug 2025, 15:42 UTC
Originally published on: 🕒 23 May 2025, 15:15 UTC

Time between publication and last update: 82 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-25110 Vulnerability Summary

CVE-2018-25110: Marked prior to version 0.3.17 is vulnerable to a Regular Expression Denial of Service (ReDoS) attack due to catastrophic backtracking in several regular expressions used for parsing HTML tags and markdown links. An attacker can exploit this vulnerability by providing specially crafted markdown input, such as deeply nested or repetitively structured brackets or tag attributes, which cause the parser to hang and lead to a Denial of Service.

Assessing the Risk of CVE-2018-25110

Access Complexity Graph

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

With low attack complexity and no required privileges, CVE-2018-25110 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-25110, 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-25110, 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-25110 has no significant impact on data confidentiality.
  • Integrity: None
    CVE-2018-25110 poses no threat to data integrity.
  • Availability: High
    CVE-2018-25110 can disrupt system operations, potentially causing complete denial of service (DoS).

CVE-2018-25110 References

External References

CWE Common Weakness Enumeration

CWE-1333

CAPEC Common Attack Pattern Enumeration and Classification

  • Regular Expression Exponential Blowup CAPEC-492 An adversary may execute an attack on a program that uses a poor Regular Expression(Regex) implementation by choosing input that results in an extreme situation for the Regex. A typical extreme situation operates at exponential time compared to the input size. This is due to most implementations using a Nondeterministic Finite Automaton(NFA) state machine to be built by the Regex algorithm since NFA allows backtracking and thus more complex regular expressions.

Vulnerable Configurations

  • cpe:2.3:a:marked_project:marked:0.0.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:marked_project:marked:0.0.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:marked_project:marked:0.0.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:marked_project:marked:0.0.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:marked_project:marked:0.0.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:marked_project:marked:0.0.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:marked_project:marked:0.0.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:marked_project:marked:0.0.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:marked_project:marked:0.0.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:marked_project:marked:0.0.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:marked_project:marked:0.0.6:*:*:*:*:node.js:*:*
    cpe:2.3:a:marked_project:marked:0.0.6:*:*:*:*:node.js:*:*
  • cpe:2.3:a:marked_project:marked:0.0.7:*:*:*:*:node.js:*:*
    cpe:2.3:a:marked_project:marked:0.0.7:*:*:*:*:node.js:*:*
  • cpe:2.3:a:marked_project:marked:0.0.8:*:*:*:*:node.js:*:*
    cpe:2.3:a:marked_project:marked:0.0.8:*:*:*:*:node.js:*:*
  • cpe:2.3:a:marked_project:marked:0.0.9:*:*:*:*:node.js:*:*
    cpe:2.3:a:marked_project:marked:0.0.9:*:*:*:*:node.js:*:*
  • cpe:2.3:a:marked_project:marked:0.1.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:marked_project:marked:0.1.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:marked_project:marked:0.1.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:marked_project:marked:0.1.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:marked_project:marked:0.1.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:marked_project:marked:0.1.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:marked_project:marked:0.1.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:marked_project:marked:0.1.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:marked_project:marked:0.1.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:marked_project:marked:0.1.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:marked_project:marked:0.1.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:marked_project:marked:0.1.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:marked_project:marked:0.1.6:*:*:*:*:node.js:*:*
    cpe:2.3:a:marked_project:marked:0.1.6:*:*:*:*:node.js:*:*
  • cpe:2.3:a:marked_project:marked:0.1.7:*:*:*:*:node.js:*:*
    cpe:2.3:a:marked_project:marked:0.1.7:*:*:*:*:node.js:*:*
  • cpe:2.3:a:marked_project:marked:0.1.8:*:*:*:*:node.js:*:*
    cpe:2.3:a:marked_project:marked:0.1.8:*:*:*:*:node.js:*:*
  • cpe:2.3:a:marked_project:marked:0.1.9:*:*:*:*:node.js:*:*
    cpe:2.3:a:marked_project:marked:0.1.9:*:*:*:*:node.js:*:*
  • cpe:2.3:a:marked_project:marked:0.2.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:marked_project:marked:0.2.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:marked_project:marked:0.2.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:marked_project:marked:0.2.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:marked_project:marked:0.2.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:marked_project:marked:0.2.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:marked_project:marked:0.2.2-1:*:*:*:*:node.js:*:*
    cpe:2.3:a:marked_project:marked:0.2.2-1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:marked_project:marked:0.2.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:marked_project:marked:0.2.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:marked_project:marked:0.2.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:marked_project:marked:0.2.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:marked_project:marked:0.2.4-1:*:*:*:*:node.js:*:*
    cpe:2.3:a:marked_project:marked:0.2.4-1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:marked_project:marked:0.2.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:marked_project:marked:0.2.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:marked_project:marked:0.2.5c:*:*:*:*:node.js:*:*
    cpe:2.3:a:marked_project:marked:0.2.5c:*:*:*:*:node.js:*:*
  • cpe:2.3:a:marked_project:marked:0.2.6:*:*:*:*:node.js:*:*
    cpe:2.3:a:marked_project:marked:0.2.6:*:*:*:*:node.js:*:*
  • cpe:2.3:a:marked_project:marked:0.2.7:*:*:*:*:node.js:*:*
    cpe:2.3:a:marked_project:marked:0.2.7:*:*:*:*:node.js:*:*
  • cpe:2.3:a:marked_project:marked:0.2.8:*:*:*:*:node.js:*:*
    cpe:2.3:a:marked_project:marked:0.2.8:*:*:*:*:node.js:*:*
  • cpe:2.3:a:marked_project:marked:0.2.9:*:*:*:*:node.js:*:*
    cpe:2.3:a:marked_project:marked:0.2.9:*:*:*:*:node.js:*:*
  • cpe:2.3:a:marked_project:marked:0.2.10:*:*:*:*:node.js:*:*
    cpe:2.3:a:marked_project:marked:0.2.10:*:*:*:*:node.js:*:*
  • cpe:2.3:a:marked_project:marked:0.3.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:marked_project:marked:0.3.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:marked_project:marked:0.3.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:marked_project:marked:0.3.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:marked_project:marked:0.3.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:marked_project:marked:0.3.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:marked_project:marked:0.3.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:marked_project:marked:0.3.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:marked_project:marked:0.3.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:marked_project:marked:0.3.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:marked_project:marked:0.3.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:marked_project:marked:0.3.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:marked_project:marked:0.3.6:*:*:*:*:node.js:*:*
    cpe:2.3:a:marked_project:marked:0.3.6:*:*:*:*:node.js:*:*
  • cpe:2.3:a:marked_project:marked:0.3.7:*:*:*:*:node.js:*:*
    cpe:2.3:a:marked_project:marked:0.3.7:*:*:*:*:node.js:*:*
  • cpe:2.3:a:marked_project:marked:0.3.9:*:*:*:*:node.js:*:*
    cpe:2.3:a:marked_project:marked:0.3.9:*:*:*:*:node.js:*:*
  • cpe:2.3:a:marked_project:marked:0.3.12:*:*:*:*:node.js:*:*
    cpe:2.3:a:marked_project:marked:0.3.12:*:*:*:*:node.js:*:*
  • cpe:2.3:a:marked_project:marked:0.3.13:*:*:*:*:node.js:*:*
    cpe:2.3:a:marked_project:marked:0.3.13:*:*:*:*:node.js:*:*
  • cpe:2.3:a:marked_project:marked:0.3.14:*:*:*:*:node.js:*:*
    cpe:2.3:a:marked_project:marked:0.3.14:*:*:*:*:node.js:*:*
  • cpe:2.3:a:marked_project:marked:0.3.15:*:*:*:*:node.js:*:*
    cpe:2.3:a:marked_project:marked:0.3.15:*:*:*:*:node.js:*:*
  • cpe:2.3:a:marked_project:marked:0.3.16:*:*:*:*:node.js:*:*
    cpe:2.3:a:marked_project:marked:0.3.16:*:*:*:*:node.js:*:*

Protect Your Infrastructure against CVE-2018-25110: 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-57800 – Audiobookshelf is an open-source self-hosted audiobook server. In versions 2.6.0 through 2.26.3, the application does not properly restrict redirec...
  • CVE-2025-57771 – Roo Code is an AI-powered autonomous coding agent that lives in users' editors. In versions prior to 3.25.5, Roo-Code fails to properly handle proc...
  • CVE-2025-57770 – The open-source identity infrastructure software Zitadel allows administrators to disable the user self-registration. Versions 4.0.0 to 4.0.2, 3.0....
  • CVE-2025-57105 – The DI-7400G+ router has a command injection vulnerability, which allows attackers to execute arbitrary commands on the device. The sub_478D28 func...
  • CVE-2025-55745 – UnoPim is an open-source Product Information Management (PIM) system built on the Laravel framework. Versions 0.3.0 and prior are vulnerable to CSV...