From a8585067b63c396dd84a699a40d0e0652acae524 Mon Sep 17 00:00:00 2001
From: Anthony Ettinger <anthony@chovy.com>
Date: Sun, 30 Aug 2026 13:33:18 +0000
Subject: [PATCH] fix(fleet): the sudo password was being executed as a command
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Reported from the desktop, and reproducible in one line:

    /bin/sh: 1: <the password>: not found

`sudo -S` reads the password from stdin **only when it actually needs one**.
Under NOPASSWD, a still-valid sudo timestamp, or a login that is already
root, it reads nothing at all — and the password, which was prepended to the
script on the same stream, falls through to `sh -es` and runs as command
number one. Which also puts it in an error message.

That is not a corner case. It is what happens on every deploy account
configured the way deploy accounts are configured, and it is why the feature
looked fine in review: the mechanism is correct exactly when sudo challenges
you, and silently wrong when it does not.

The fix is to stop sharing the stream. With a sudo password the script now
travels as a quoted argument (`sh -ec '<script>'`) and stdin carries the
password alone, so there is no ordering to get right. `withSudoPassword`
throws rather than proceeding if it is ever handed a command whose stdin is
already occupied, and rejects a password containing a newline — which cannot
be escaped, only refused, since the newline would end the line sudo reads and
hand the remainder to the command.

Everywhere else is untouched: with no sudo, or `sudo -n`, the script still
goes on stdin, where nothing is quoted so nothing can be misquoted and a
script is not bounded by the command-line length limit.

Also: a refused password now says so. sudo emits both "Authentication failed,
try again" and "authentication required but not attempted" on a failed
attempt, and matching the second told someone who *had* supplied a password
to supply one.

Verified against real hosts rather than by reading, using root@localhost
(passwordless sudo, the broken case) and anthony@localhost (sudo does
challenge):

- password mode where sudo wants nothing: script runs, password is not
  executed, nothing leaks to stderr
- password mode with a WRONG password where sudo does challenge: refused, the
  script does not run, the password is not echoed back
- a script of quotes, backticks, `$VAR`, pipes and redirects survives the
  quoted argument byte for byte
- `sudo off` and `sudo -n` unchanged

Two tests asserted the old behaviour and were codifying the bug; they now
assert the invariant instead — in password mode `stdin` is the password and
only the password.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UeSWg1Czsb2Lwxj8vHUnA4
---
 packages/fleet-core/src/command.test.ts | 51 ++++++++++++++--
 packages/fleet-core/src/command.ts      | 78 +++++++++++++++++++++----
 2 files changed, 114 insertions(+), 15 deletions(-)

diff --git a/packages/fleet-core/src/command.test.ts b/packages/fleet-core/src/command.test.ts
index 496d535..a985de6 100644
--- a/packages/fleet-core/src/command.test.ts
+++ b/packages/fleet-core/src/command.test.ts
@@ -28,9 +28,29 @@ describe('buildCommand', () => {
     expect(buildCommand({ script: 'id', interpreter: 'sh', sudo: 'non-interactive' }).command).toBe('sudo -n /bin/sh -es')
   })
 
-  it('uses sudo -S with an empty prompt when a password will be supplied', () => {
+  it('leaves stdin free for the password, and sends the script as an argument', () => {
+    // `sudo -S` reads stdin ONLY when it actually needs a password. Under
+    // NOPASSWD, a cached timestamp, or an already-root login it reads nothing,
+    // and a password prepended to the script becomes command number one:
+    //     /bin/sh: 1: <the password>: not found
     const built = buildCommand({ script: 'id', interpreter: 'sh', sudo: 'password' })
-    expect(built.command).toBe("sudo -S -p '' /bin/sh -es")
+    expect(built.command).toBe("sudo -S -p '' /bin/sh -ec id")
+    expect(built.stdin).toBeUndefined()
+  })
+
+  it('quotes that argument, so a script full of metacharacters still arrives intact', () => {
+    const built = buildCommand({
+      script: `echo "it's $(whoami)"; rm -rf /tmp/x`,
+      interpreter: 'sh',
+      sudo: 'password',
+    })
+    // Single-quoted with embedded quotes escaped: the shell sees one argument.
+    expect(built.command).toBe(`sudo -S -p '' /bin/sh -ec 'echo "it'\\''s $(whoami)"; rm -rf /tmp/x'`)
+  })
+
+  it('honours --no-fail-fast in the password path too', () => {
+    const built = buildCommand({ script: 'id', interpreter: 'sh', sudo: 'password', failFast: false })
+    expect(built.command).toBe("sudo -S -p '' /bin/sh -c id")
   })
 
   it('runs raw text unwrapped, with nothing on stdin', () => {
@@ -73,9 +93,22 @@ describe('buildCommand', () => {
 })
 
 describe('withSudoPassword', () => {
-  it('puts the password on the first stdin line, ahead of the script', () => {
+  it('puts the password on stdin and nothing else', () => {
     const built = withSudoPassword(buildCommand({ script: 'id', interpreter: 'sh', sudo: 'password' }), 'hunter2')
-    expect(built.stdin).toBe('hunter2\nid\n')
+    expect(built.stdin).toBe('hunter2\n')
+    expect(built.stdin).not.toContain('id')
+  })
+
+  it('refuses to share stdin with a script rather than corrupting the run', () => {
+    // The old behaviour. If buildCommand ever leaves a script on stdin in this
+    // mode again, this throws instead of executing a password.
+    const onStdin = buildCommand({ script: 'id', interpreter: 'sh', sudo: 'off' })
+    expect(() => withSudoPassword(onStdin, 'hunter2')).toThrow(/cannot share stdin/)
+  })
+
+  it('refuses a password containing a newline, which cannot be escaped', () => {
+    const built = buildCommand({ script: 'id', interpreter: 'sh', sudo: 'password' })
+    expect(() => withSudoPassword(built, 'two\nlines')).toThrow(/newline/)
   })
 
   it('leaves the display form alone, so a password cannot reach a log through it', () => {
@@ -84,7 +117,7 @@ describe('withSudoPassword', () => {
     expect(withSudoPassword(base, 'hunter2').display).not.toContain('hunter2')
   })
 
-  it('works for raw commands, which have no script on stdin of their own', () => {
+  it('works for raw commands, which never had a script on stdin', () => {
     const built = withSudoPassword(buildCommand({ script: 'id', interpreter: 'raw', sudo: 'password' }), 'hunter2')
     expect(built.stdin).toBe('hunter2\n')
   })
@@ -106,6 +139,14 @@ describe('explainSudoFailure', () => {
     }
   })
 
+  it('tells someone who supplied a password that it was refused, not to supply one', () => {
+    // sudo says both things on a failed attempt: the refusal, then
+    // "authentication required but not attempted" once it runs out of input.
+    const stderr = 'sudo: Authentication failed, try again.\nsudo: Authentication required but not attempted'
+    expect(explainSudoFailure(stderr)).toMatch(/refused/)
+    expect(explainSudoFailure(stderr)).not.toMatch(/--sudo-password/)
+  })
+
   it('stays out of the way of unrelated failures', () => {
     expect(explainSudoFailure('nginx: configuration file test failed')).toBeNull()
     expect(explainSudoFailure('sudo: unable to resolve host web-01')).toBeNull()
diff --git a/packages/fleet-core/src/command.ts b/packages/fleet-core/src/command.ts
index 678a87c..dacde06 100644
--- a/packages/fleet-core/src/command.ts
+++ b/packages/fleet-core/src/command.ts
@@ -110,11 +110,40 @@ export function buildCommand(options: BuildOptions): BuiltCommand {
   }
 
   const binary = INTERPRETER_BINARY[interpreter]
+  const errexit = options.failFast === false ? '' : 'e'
+
+  /*
+   * With a sudo password, stdin belongs to sudo and to nothing else.
+   *
+   * `sudo -S` reads the password from stdin *only when it actually needs one*.
+   * Under NOPASSWD, a cached timestamp, or when the login is already root, it
+   * reads nothing — and the password line then falls through to `sh -es` and
+   * is executed as command number one:
+   *
+   *     /bin/sh: 1: <the password>: not found
+   *
+   * That is not a corner case; it is what happens on every correctly
+   * configured deploy account. So in this mode the script travels as a
+   * quoted argument instead, and stdin carries the password alone. There is
+   * no ordering to get right because the two never share a stream.
+   */
+  if (sudo === 'password') {
+    const command = `${cd}${sudoPrefix(sudo)}${env}${binary} -${errexit}c ${shellQuote(script)}`
+    return {
+      command,
+      // The password is added by `withSudoPassword`, and it is all that ever
+      // goes to stdin here.
+      stdin: undefined,
+      display: `${cd}sudo -S ${env}${binary} -${errexit}c  <<'DISKPUSH'\n${script.trimEnd()}\nDISKPUSH`,
+    }
+  }
+
   // `-s` makes the interpreter read the script from stdin while still
-  // accepting arguments; `-e` stops at the first failing command.
-  const flags = options.failFast === false ? '-s' : '-es'
-  const inner = `${env}${binary} ${flags}`
-  const command = `${cd}${sudoPrefix(sudo)}${inner}`
+  // accepting arguments; `-e` stops at the first failing command. Preferred
+  // wherever stdin is free: nothing is quoted, so nothing can be misquoted,
+  // and a script is not bounded by the command-line length limit.
+  const flags = `-${errexit}s`
+  const command = `${cd}${sudoPrefix(sudo)}${env}${binary} ${flags}`
 
   return {
     command,
@@ -124,15 +153,31 @@ export function buildCommand(options: BuildOptions): BuiltCommand {
 }
 
 /**
- * Prepends the sudo password to whatever the process reads first.
+ * Puts the sudo password on stdin, and nothing else.
  *
- * `sudo -S` takes the password as the first line on stdin and hands the rest
- * to the command it runs, so a shell script piped in behind it still arrives
- * intact. Kept separate from `buildCommand` so the password never travels
- * through the same object that gets logged.
+ * It used to prepend the password to the script, on the theory that `sudo -S`
+ * eats the first line and hands the rest on. It does — but only when it needs
+ * a password at all. Under NOPASSWD, a cached timestamp, or an already-root
+ * login it reads nothing, the shell gets the password as its first command,
+ * and the run dies with `<password>: not found` — leaking the password into
+ * an error message on the way.
+ *
+ * `buildCommand` therefore routes the script through an argument whenever
+ * this mode is used, leaving stdin free. Refuses rather than silently
+ * corrupting if that ever stops being true.
+ *
+ * Kept separate from `buildCommand` so the password never travels through the
+ * object that gets logged: `display` is built before this is called and is
+ * not touched by it.
  */
 export function withSudoPassword(built: BuiltCommand, password: string): BuiltCommand {
-  return { ...built, stdin: `${password}\n${built.stdin ?? ''}` }
+  if (built.stdin !== undefined) {
+    throw new Error('A sudo password cannot share stdin with a script; buildCommand should have left it free.')
+  }
+  // A password containing a newline would end the line sudo reads and send
+  // the remainder to the command. It cannot be escaped, only rejected.
+  if (/[\r\n]/.test(password)) throw new Error('A sudo password cannot contain a newline.')
+  return { ...built, stdin: `${password}\n` }
 }
 
 /**
@@ -150,7 +195,20 @@ export function withSudoPassword(built: BuiltCommand, password: string): BuiltCo
 const SUDO_NEEDS_AUTH =
   /sudo:.*(password is required|interactive authentication is required|a terminal is required|no askpass program|must have a tty)/i
 
+/**
+ * A password that was supplied and refused.
+ *
+ * Checked first, because sudo says both things on a failed attempt — the
+ * refusal, and then "authentication required but not attempted" once it runs
+ * out of input. Reporting the second would tell someone who *did* supply a
+ * password to supply one.
+ */
+const SUDO_REJECTED = /sudo:.*(authentication failed|sorry, try again|incorrect password)/i
+
 export function explainSudoFailure(stderr: string): string | null {
+  if (SUDO_REJECTED.test(stderr)) {
+    return 'The sudo password was refused by this server. Nothing was run.'
+  }
   if (!SUDO_NEEDS_AUTH.test(stderr)) return null
   return (
     'sudo on this server wants a password. Re-run with --sudo-password to be asked for it once, ' +