Command execution via malformed OSC 50 reply
Published Nov 10, 2022 · Updated Apr 8, 2026
Command injection in xterm before 375 allows attackers to execute shell commands when crafted OSC 50 terminal data is processed. A failed font selection remains queryable, so the OSC 50 reply echoes attacker-controlled text and permits Ctrl-G termination. Exploitation requires enabled font operations and Zsh vi line-editing mode, where Ctrl-G invokes list-expand and executes expansion commands without Enter.
Summary
What happened
Command injection in xterm before 375 allows attackers to execute shell commands when crafted OSC 50 terminal data is processed. A failed font selection remains queryable, so the OSC 50 reply echoes attacker-controlled text and permits Ctrl-G termination. Exploitation requires enabled font operations and Zsh vi line-editing mode, where Ctrl-G invokes list-expand and executes expansion commands without Enter.
The record
- CVE
- CVE-2022-45063
- Published
- Nov 10, 2022
- Updated
- Apr 8, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-77, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 10, 2022CVE publishedPublication date reported by the CVE source.
- Apr 8, 2026Record 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
- OSC 50 Zsh vi-mode 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