GPU VulnDB

Database/Kernel, userspace & hypervisor

OpenSSH ssh client: NUL byte in an ssh:// URI can execute commands via ProxyCommand

CVSS 3.6CVE-2025-61985Kernel, userspace & hypervisorcurated

Impact

The ssh client before 10.1 allows a '\0' character inside an ssh:// URI, which can lead to command execution when a ProxyCommand is configured. This is a distinct code path from the control-character username issue fixed in the same release: here the hostile input is a URI rather than a username. Operators are exposed wherever tooling hands an externally supplied ssh:// URI to the ssh client on a bastion, build runner or scheduler node - the command runs locally as the automation account before any remote authentication happens. Clusters that only ever call ssh with fixed hostnames from trusted config are not affected.

Who can reach it

Local. Requires something to pass an attacker-controlled ssh:// URI to the ssh client on a host that has ProxyCommand in effect. No credentials on the destination host are required.

What to do

Upgrade OpenSSH to 10.1p1 or a vendor backport. Client-side package update only - no daemon restart, node drain or reboot. Interim mitigation is to validate or reject ssh:// URIs that come from outside before invoking ssh. Siemens advisory SSA-019113 covers the affected SIMATIC S7-1500 MFP CPUs, which need their own firmware path.

References

Related entries

All Kernel, userspace & hypervisor entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.