CVE-2025-6492
BaseFortify
Publication date: 2025-06-22
Last updated on: 2025-06-23
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-1333 | The product uses a regular expression with an inefficient, possibly exponential worst-case computational complexity that consumes excessive CPU cycles. |
| CWE-400 | The product does not properly control the allocation and maintenance of a limited resource. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-6492 is a Regular Expression Denial of Service (ReDoS) vulnerability in MarkText up to version 0.17.1. It occurs in the function getRecommendTitleFromMarkdownString in the file index.js, where an inefficient regular expression with potentially exponential complexity is used. When an attacker provides specially crafted Markdown content, the regular expression engine experiences excessive backtracking, causing high CPU usage, application freezing, or unresponsiveness. This attack can be launched remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can impact you by causing a denial of service condition in the MarkText application. Specifically, it can lead to severe performance degradation or application unresponsiveness due to excessive CPU consumption triggered by maliciously crafted input. This can disrupt normal usage, potentially causing downtime or loss of availability of the affected software. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring for unusually high CPU usage or application unresponsiveness when MarkText processes Markdown content, especially if maliciously crafted code blocks are involved. Since the issue is caused by inefficient regular expression complexity in the function getRecommendTitleFromMarkdownString, you can test the application by feeding it specially crafted Markdown input designed to trigger excessive backtracking. There is a public proof-of-concept exploit available on GitHub that can be used to verify the vulnerability. Additionally, reviewing logs or using performance monitoring tools to detect prolonged execution times or freezes in MarkText can help identify exploitation attempts. Specific commands are not provided in the resources. [1, 2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include updating MarkText to a version where the problematic regular expression has been fixed as per the pull request that modifies the regex pattern to reduce catastrophic backtracking. If an update is not available, consider implementing a timeout mechanism for regular expression evaluation to prevent prolonged execution. Alternatively, avoid processing untrusted Markdown content with the vulnerable version of MarkText or replace the affected component with an alternative product. No other known countermeasures or mitigations have been identified. [2, 3]