LiveActive security incident?Get immediate response
CVE Record

CVE-2015-10005: markdown-it html_re.js redos

A vulnerability was found in markdown-it up to 2.x. It has been classified as problematic. Affected is an unknown function of the file lib/common/html_re.js. The manipulation leads to inefficient regular expression complexity. Upgrading to version 3.0.0 is able to address this issue. The name of the patch is 89c8620157d6e38f9872811620d25138fc9d1b0d. It is recommended to upgrade the affected component. The identifier of this vulnerability is VDB-216852.

LowCVSS 3.5Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

CVE-2015-10005 is a low-severity denial-of-service risk in markdown-it 2.x. A crafted Markdown input may make a regular expression consume excessive processing time, reducing availability where the library handles untrusted content. The cited fix is upgrading to markdown-it 3.0.0.

Executive priority

Treat this as routine patching unless markdown-it 2.x processes public content in a critical service. It is not a known exploited issue in the supplied sources, but it can still affect service availability.

Technical view

The issue is classified as CWE-1333, inefficient regular expression complexity, in markdown-it's lib/common/html_re.js. The CVSS 3.1 score is 3.5 with low availability impact and no confidentiality or integrity impact. The referenced patch is commit 89c8620157d6e38f9872811620d25138fc9d1b0d, released in 3.0.0.

Likely exposure

Exposure is most likely in applications still using markdown-it 2.x, especially where users can submit Markdown that is parsed server-side or in shared worker processes. The source bundle does not identify specific downstream products or platforms.

Exploitation context

The source bundle does not report active exploitation, and KEV status is false. The risk is resource exhaustion rather than data theft or code execution. Practical impact depends on whether attackers can reach a Markdown parsing path.

Researcher notes

Evidence names the vulnerable file and fixed release, but not the exact affected function or triggering input. Validate exposure through dependency inventory and reachable Markdown parsing flows rather than assuming every installation is exploitable.

Mitigation direction

  • Upgrade markdown-it to version 3.0.0 or later.
  • Prioritize systems parsing untrusted or public Markdown input.
  • Check vendor guidance for any downstream packaged versions.
  • Apply compensating request limits where upgrade timing is constrained.

Validation and detection

  • Search package manifests and lockfiles for markdown-it 2.x.
  • Confirm deployed artifacts use markdown-it 3.0.0 or later.
  • Map routes or jobs that parse user-provided Markdown.
  • Review monitoring for unusual Markdown parsing latency or worker saturation.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-1333: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2015-10005 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Low
CVSS
3.5 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
3.5CVSS 3.1LowCVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L2.11.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

3.5Low
CVSS 3.1 vector shape for CVE-2015-10005Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/amarkdown-it2.xListed
Weakness

CWE details

CWE-1333

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-1333 · source CWE mapping

Inefficient Regular Expression Complexity

Inefficient Regular Expression Complexity represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs