Arbitrary code execution via trusted remote Org files
Published Mar 25, 2024 · Updated Dec 3, 2024
Improper trust handling in GNU Emacs before 29.3 and Org Mode before 9.6.23 allows attackers to run code through remote Org files. The org-file-contents function recognizes URL syntax but does not call file-remote-p, so TRAMP-fetched content bypasses the untrusted-content path. A user must open a crafted remote Org file, after which embedded content executes with the user's Emacs privileges.
Summary
What happened
Improper trust handling in GNU Emacs before 29.3 and Org Mode before 9.6.23 allows attackers to run code through remote Org files. The org-file-contents function recognizes URL syntax but does not call file-remote-p, so TRAMP-fetched content bypasses the untrusted-content path. A user must open a crafted remote Org file, after which embedded content executes with the user's Emacs privileges.
The record
- CVE
- CVE-2024-30205
- Published
- Mar 25, 2024
- Updated
- Dec 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-494, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 25, 2024CVE publishedPublication date reported by the CVE source.
- Dec 3, 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.
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
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