Thanks, this worked.

On 2025-05-13 02:47, Matt Johnston wrote: dbclient 'localhost,|touch 123 ' 2. Both dbclient and ssh are symlinks to the same dropbear binary. Does this CVE apply equally to both, or is it specific to dbclient? It applies to both.

Hi!

On 2025-05-09 18:15, Alan Coopersmith wrote: https://lists.ucc.gu.uwa.edu.au/pipermail/dropbear/2025q2/002385.html announces the release of Dropbear SSH 2025.88 including this fix: - Security: Don't allow dbclient hostname arguments to be interpreted   by the shell.

dbclient hostname arguments with a comma (for multihop) would be   passed to the shell which could result in running arbitrary shell   commands locally. That could be a security issue in situations   where dbclient is passed untrusted hostname arguments.

Now the multihop command is executed directly, no shell is involved.   Thanks to Marcin Nowak for the report, tracked as CVE-2025-47203

I have two main questions:

Thanks in advance,

Albert

https://lists.ucc.gu.uwa.edu.au/pipermail/dropbear/2025q2/002385.html announces the release of Dropbear SSH 2025.88 including this fix: - Security: Don't allow dbclient hostname arguments to be interpreted by the shell.

dbclient hostname arguments with a comma (for multihop) would be passed to the shell which could result in running arbitrary shell commands locally. That could be a security issue in situations where dbclient is passed untrusted hostname arguments.

Now the multihop command is executed directly, no shell is involved. Thanks to Marcin Nowak for the report, tracked as CVE-2025-47203 -- -Alan Coopersmith- alan.coopersmith () oracle com Oracle Solaris Engineering - https://blogs.oracle.com/solaris

An issue was discovered in Dropbear through 2020.81. Due to a non-RFC-compliant check of the available authentication methods in the client-side SSH code, it is possible for an SSH server to change the login process in its favor. This attack can bypass additional security measures such as FIDO2 tokens or SSH-Askpass. Thus, it allows an attacker to abuse a forwarded agent for logging on to another server unnoticed.

scp.c in Dropbear before 2020.79 mishandles the filename of . or an empty filename, a related issue to CVE-2018-20685.

Dropbear 2011.54 through 2018.76 has an inconsistent failure delay that may lead to revealing valid usernames, a different issue than CVE-2018-15599.

It was found that dropbear before version 2013.59 with GSSAPI leaks whether given username is valid or invalid. When an invalid username is given, the GSSAPI authentication failure was incorrectly counted towards the maximum allowed number of password attempts.

The recvmsguserauthrequest function in svr-auth.c in Dropbear through 2018.76 is prone to a user enumeration vulnerability because username validity affects how fields in SSHMSGUSERAUTH messages are handled, a similar issue to CVE-2018-15473 in an unrelated codebase.

CRLF injection vulnerability in Dropbear SSH before 2016.72 allows remote authenticated users to bypass intended shell-command restrictions via crafted X11 forwarding data.

The bufdecompress function in packet.c in Dropbear SSH Server before 2013.59 allows remote attackers to cause a denial of service (memory consumption) via a compressed packet that has a large size when it is decompressed.

Dropbear SSH Server before 2013.59 generates error messages for a failed logon attempt with different time delays depending on whether the user account exists, which allows remote attackers to discover valid usernames.

Use-after-free vulnerability in Dropbear SSH Server 0.52 through 2012.54, when command restriction and public key authentication are enabled, allows remote authenticated users to execute arbitrary code and bypass command restrictions via multiple crafted command requests, related to "channels concurrency."