Arbitrary code execution via unsafe eval
Published Nov 4, 2021 · Updated Aug 4, 2024
Code injection in Obsidian Dataview through 0.4.12-hotfix1 allows attackers to execute arbitrary code via malicious Markdown files opened by users. The evalInContext function in src/api/inline-api.ts passes user-supplied JavaScript to unsafe eval, enabling commands such as child_process execution. Exploitation requires a user to open the crafted file; execution occurs with that user's Obsidian privileges.
Summary
What happened
Code injection in Obsidian Dataview through 0.4.12-hotfix1 allows attackers to execute arbitrary code via malicious Markdown files opened by users. The evalInContext function in src/api/inline-api.ts passes user-supplied JavaScript to unsafe eval, enabling commands such as child_process execution. Exploitation requires a user to open the crafted file; execution occurs with that user's Obsidian privileges.
The record
- CVE
- CVE-2021-42057
- Published
- Nov 4, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-94, T1059.007
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 4, 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
- CVE-2021-42057 malicious Markdown 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