Command execution via unchecked proxy hostname
Published Jan 3, 2024 · Updated Nov 7, 2025
Command injection in libssh on Red Hat Enterprise Linux 8 and 9 allows local users to execute shell commands through a crafted hostname. ProxyCommand and ProxyJump expand an unchecked hostname into a shell command, allowing metacharacters to alter the command being executed. Exploitation requires low-privileged local access and user interaction, and commands run with the invoking client's privileges.
Summary
What happened
Command injection in libssh on Red Hat Enterprise Linux 8 and 9 allows local users to execute shell commands through a crafted hostname. ProxyCommand and ProxyJump expand an unchecked hostname into a shell command, allowing metacharacters to alter the command being executed. Exploitation requires low-privileged local access and user interaction, and commands run with the invoking client's privileges.
The record
- CVE
- CVE-2023-6004
- Published
- Jan 3, 2024
- Updated
- Nov 7, 2025
- Vendor
- Red Hat
- Product
- Red Hat Enterprise Linux 8
- Classifications
- CWE-74, T1204, T1059
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 3, 2024CVE publishedPublication date reported by the CVE source.
- Nov 7, 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?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
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
- poc-proxycommand-vulnerableproof 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