Command execution via unquoted etags filenames
Published Feb 20, 2023 · Updated Mar 18, 2025
Command injection in GNU Emacs etags 28.2 and earlier allows local users to execute commands through crafted source-file names. The lib-src/etags.c implementation passes a constructed shell command to system() without quoting file-name arguments containing shell metacharacters. Exploitation requires a victim to invoke etags on attacker-influenced directory contents; injected commands run with that account's privileges.
Summary
What happened
Command injection in GNU Emacs etags 28.2 and earlier allows local users to execute commands through crafted source-file names. The lib-src/etags.c implementation passes a constructed shell command to system() without quoting file-name arguments containing shell metacharacters. Exploitation requires a victim to invoke etags on attacker-influenced directory contents; injected commands run with that account's privileges.
The record
- CVE
- CVE-2022-48337
- Published
- Feb 20, 2023
- Updated
- Mar 18, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-78, T1059.004
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Feb 20, 2023CVE publishedPublication date reported by the CVE source.
- Mar 18, 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?
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