Local file disclosure via rendered JavaScript
Published Nov 3, 2022 · Updated May 5, 2025
Local file disclosure in Markdownify 1.4.1 allows attackers to read arbitrary files by inducing a user to open malicious Markdown. Its live preview renders embedded JavaScript from the document without an effective Content Security Policy or adequate content validation, letting script fetch local file resources. Exploitation requires a user to open the crafted file, and the demonstrated consequence is disclosure of files readable by the application.
Summary
What happened
Local file disclosure in Markdownify 1.4.1 allows attackers to read arbitrary files by inducing a user to open malicious Markdown. Its live preview renders embedded JavaScript from the document without an effective Content Security Policy or adequate content validation, letting script fetch local file resources. Exploitation requires a user to open the crafted file, and the demonstrated consequence is disclosure of files readable by the application.
The record
- CVE
- CVE-2022-41710
- Published
- Nov 3, 2022
- Updated
- May 5, 2025
- Vendor
- Matthew Tretter
- Product
- Markdownify
- Classifications
- CWE-552, T1005, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 3, 2022CVE publishedPublication date reported by the CVE source.
- May 5, 2025Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.4.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- Fluid Attacks malicious Markdown local-file-read proof of conceptproof of concept · demonstrated
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