ssh in OpenSSH before 10.1 allows control characters in usernames that originate from certain possibly untrusted sources, potentially leading to code execution when a ProxyCommand is used. The untrusted sources are the command line and %-sequence expansion of a configuration file. (A configuration file that provides a complete literal username is not categorized as an untrusted source.)
Weakness
The product does not properly filter, remove, quote, or otherwise manage the invalid use of special elements in user-controlled input, which could cause adverse effect on its behavior and integrity.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | RedHat | openssh-0:9.9p1-12.el10_1 | * |
| Red Hat Enterprise Linux 8 | RedHat | openssh-0:8.0p1-27.el8_10 | * |
| Red Hat Enterprise Linux 8 | RedHat | openssh-0:8.0p1-27.el8_10 | * |
| Red Hat Enterprise Linux 9 | RedHat | openssh-0:8.7p1-47.el9_7 | * |
| Red Hat Enterprise Linux 9 | RedHat | openssh-0:8.7p1-47.el9_7 | * |
| Red Hat Enterprise Linux 9.4 Extended Update Support | RedHat | openssh-0:8.7p1-38.el9_4.6 | * |
| Red Hat Enterprise Linux 9.6 Extended Update Support | RedHat | openssh-0:8.7p1-45.el9_6.1 | * |
| Red Hat Discovery 2 | RedHat | discovery/discovery-server-rhel9:sha256:d4e8987a100ea60942306f1564679e51fa1364f6124fbfb3100959f83a1f16bf | * |
| Red Hat Update Infrastructure 5 | RedHat | rhui5/installer-rhel9:sha256:e1d64fbd0e4b90259d9fbb94736ed74c7c384d13067c6bbbb107c664683cb1a9 | * |
| Red Hat Update Infrastructure 5 | RedHat | rhui5/rhua-rhel9:sha256:4642951a6a57511f8b481a6481fcd417fc7f3de86511cdab28b9b89639c2bdb2 | * |
| Openssh | Ubuntu | plucky | * |
| Openssh | Ubuntu | upstream | * |
| Openssh-ssh1 | Ubuntu | devel | * |
| Openssh-ssh1 | Ubuntu | esm-apps/focal | * |
| Openssh-ssh1 | Ubuntu | esm-apps/jammy | * |
| Openssh-ssh1 | Ubuntu | esm-apps/noble | * |
| Openssh-ssh1 | Ubuntu | jammy | * |
| Openssh-ssh1 | Ubuntu | noble | * |
| Openssh-ssh1 | Ubuntu | plucky | * |
| Openssh-ssh1 | Ubuntu | questing | * |
| Openssh-ssh1 | Ubuntu | upstream | * |
Potential Mitigations
- Assume all input is malicious. Use an “accept known good” input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
- When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, “boat” may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as “red” or “blue.”
- Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code’s environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
References
- https://marc.info/?l=openssh-unix-dev\u0026m=175974522032149\u0026w=2
- https://www.openssh.com/releasenotes.html#10.1p1
- https://www.openwall.com/lists/oss-security/2025/10/06/1
- http://www.openwall.com/lists/oss-security/2025/10/07/1
- http://www.openwall.com/lists/oss-security/2025/10/12/1
- https://www.vicarius.io/vsociety/posts/cve-2025-61984-detection-script-remote-code-execution-vulnerability-affecting-openssh
- https://www.vicarius.io/vsociety/posts/cve-2025-61984-mitigation-script-remote-code-execution-vulnerability-affecting-openssh
- https://dgl.cx/2025/10/bash-a-newline-ssh-proxycommand-cve-2025-61984