credential: avoid writing values with newlines

The credential protocol that we use to speak to helpers can't represent
values with newlines in them. This was an intentional design choice to
keep the protocol simple, since none of the values we pass should
generally have newlines.

However, if we _do_ encounter a newline in a value, we blindly transmit
it in credential_write(). Such values may break the protocol syntax, or
worse, inject new valid lines into the protocol stream.

The most likely way for a newline to end up in a credential struct is by
decoding a URL with a percent-encoded newline. However, since the bug
occurs at the moment we write the value to the protocol, we'll catch it
there. That should leave no possibility of accidentally missing a code
path that can trigger the problem.

At this level of the code we have little choice but to die(). However,
since we'd not ever expect to see this case outside of a malicious URL,
that's an acceptable outcome.

Reported-by: Felix Wilhelm <fwilhelm@google.com>
pull/779/head
Jeff King 3 years ago
parent a5ab8d0317
commit 9a6bbee800
  1. 2
      credential.c
  2. 6
      t/t0300-credentials.sh

@ -194,6 +194,8 @@ static void credential_write_item(FILE *fp, const char *key, const char *value)
{
if (!value)
return;
if (strchr(value, '\n'))
die("credential value for %s contains newline", key);
fprintf(fp, "%s=%s\n", key, value);
}

@ -309,4 +309,10 @@ test_expect_success 'empty helper spec resets helper list' '
EOF
'
test_expect_success 'url parser rejects embedded newlines' '
test_must_fail git credential fill <<-\EOF
url=https://one.example.com?%0ahost=two.example.com/
EOF
'
test_done

Loading…
Cancel
Save