ssh in OpenSSH before 10.1 allows the 0 character in an ssh:// URI, potentially leading to code execution when a ProxyCommand is used.
Weakness
The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes NUL characters or null bytes when they are sent to a downstream component.
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.