Skip to content

[sec-check] Default root password 'bluefin' + PermitRootLogin yes — remote root once sshd is enabled #168

Closed

Description

@hivecommons-hive

Security Finding

Severity: high
Type: unsafe-pattern / default-credentials

Commit 37c8356 ("fix(boot): resolve first-boot login…") reverted the sshd hardening from #29 and seeded a well-known default root password into every DDI image:

  • elements/oci/bluefin-server-ddi.bst:74 — hardcoded SHA-512 crypt hash of password bluefin written to /etc/shadow in every shipped image (hash is public in this repo, so the password is effectively published).
  • files/os/ssh/sshd_config.d/bluefin-server.conf — PermitRootLogin yes, PasswordAuthentication yes, KbdInteractiveAuthentication yes.
  • files/os/issue.d/40-kubestellar.issue — console banner advertises Default login: root / bluefin.

sshd is preset-disabled (files/os/systemd/system-preset/zz-enable-sshd.preset), but the documented bring-up path is to enable sshd for "remote diagnostics" (SSH host keys are pre-generated in the image for exactly this). The moment sshd is enabled on a network-reachable host, anyone can log in as root with password bluefin unless the operator knows to change it first. Password change is not enforced at first login (no expired-password flag — shadow entry uses 19700, a fixed last-change date).

Impact

  • Any Bluefin Server install where the operator enables sshd (the intended diagnostics path) is remotely root-compromisable with a credential printed in this public repository.
  • Same hash in every image → credential is identical fleet-wide; no per-install randomness.

Recommendation

  1. sshd drop-in: PermitRootLogin prohibit-password, PasswordAuthentication no, KbdInteractiveAuthentication no — restores [sec-check] fix: harden sshd drop-in — key-only auth, no root password login #29. Console/serial bring-up (root / bluefin via securetty) is unaffected.
  2. Better: force password rotation on first login (set shadow last-change to 0 → chage -d 0 root equivalent) or generate a per-install random password at install/first-boot time instead of baking one hash into the image.
  3. Longer term: drop the seeded password entirely; require key injection via installer/systemd credentials for remote bring-up.

A hold-gated PR restoring the sshd hardening (item 1, console bring-up preserved) accompanies this issue.


Filed by sec-check agent (ACMM L4/L5 — hold-gated mode)

🐝 Hive Agent: security | Instance: hosted-projectbluefin-knuckle-gjvq | SHA: unknown

— hive: agent=sec-check backend=copilot model=kimi-k3

Activity

  1. hivecommons-hive commented on Sep 20, 2026

    @hivecommons-hive
    ContributorAuthor

    A merged PR referenced this issue without closing it. Carrying the remainder back here so the issue timeline shows what is still open.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    agent/securityFiled or owned by the security agent.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions