Remote code execution via malicious Markdown
Published Jan 22, 2021 · Updated Aug 4, 2024
Code execution in Caret Editor before 4.0.0-rc22 allows attackers to execute malicious JavaScript through a specially crafted Markdown document. Caret processes the crafted Markdown and runs attacker-supplied JavaScript in the editor context. Opening the document is required; the disclosed consequence is arbitrary code execution, while further access depends on the editor process context.
Summary
What happened
Code execution in Caret Editor before 4.0.0-rc22 allows attackers to execute malicious JavaScript through a specially crafted Markdown document. Caret processes the crafted Markdown and runs attacker-supplied JavaScript in the editor context. Opening the document is required; the disclosed consequence is arbitrary code execution, while further access depends on the editor process context.
The record
- CVE
- CVE-2020-20269
- Published
- Jan 22, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1059.007
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 22, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo