Login
You're viewing the functional.cafe public feed.
  • Nov 6, 2026, 11:42 AM

    Did some more investigation into the #sshhole vulnerability.

    A #buildroot build is vulnerable, if you use a musl toolchain (default is glibc, former default and more commonly used in embedded is uclibc-ng), openssh (default is dropbear) and have any user with a password set up. Buildroot will create * locked accounts by default which work as a target. And password login (just not for root) is enabled by default.

    The openssh package has been updated and the fix backported to stable branches.

    💬 2🔄 0⭐ 0

Replies

  • Nov 6, 2026, 11:47 AM

    I don't think musl + openssh is a super common config. Especially because buildroot has been much more entangled with uclibc historically, which most people who want a small system would probably chose.

    But it's not an outlandish config either, I guess. And it's very unfortunate that password auth is enabled by default. :-/

    💬 0🔄 0⭐ 0
  • Nov 6, 2026, 11:50 AM

    One strange thing which I haven't understood about this yet is that you need NumberOfPasswordPrompts=2 and only the second attempt then works. (and -o PubkeyAuthentication=no to prevent trying pubkeyauth after first password failure).

    💬 1🔄 0⭐ 0
  • Nov 6, 2026, 11:53 AM

    And I think what's also relevant, though it might not actually save people:

    I don't think you can get a shell with the default setup? The locked accounts have /bin/false as a shell. You can get port forwards working though.

    💬 0🔄 0⭐ 0