git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH 2/2] vreport: sanitize ASCII control chars

From
Jeff King <peff@peff.net>
Date
Jan 11, 2017, 14:02 UTC
Message-ID
<20170111140223.7irjqrtz77kaa5r7@sigill.intra.peff.net>
In-Reply-To
<20170111140138.5p647xuqpqrej63b@sigill.intra.peff.net>

Our error() and die() calls may report messages with arbitrary data (e.g., filenames or even data from a remote server). Let's make it harder to cause confusion with mischievous filenames. E.g., try:

  git rev-parse "$(printf "\rfatal: this argument is too sneaky")" --
or
  git rev-parse "$(printf "\x1b[5mblinky\x1b[0m")" --

Let's block all ASCII control characters, with the exception of TAB and LF. We use both in our own messages (and we are necessarily sanitizing the complete output of snprintf here, as we do not have access to the individual varargs). And TAB and LF are unlikely to cause confusion (you could put "\nfatal: sneaky\n" in your filename, but it would at least not _cover up_ the message leading to it, unlike "\r").

We'll replace the characters with a "?", which is similar to how "ls" behaves. It might be nice to do something less lossy, like converting them to "\x" hex codes. But replacing with a single character makes it easy to do in-place and without worrying about length limitations. This feature should kick in rarely enough that the "?" marks are almost never seen.

We'll leave high-bit characters as-is, as they are likely to be UTF-8 (though there may be some Unicode mischief you could cause, which may require further patches).

Signed-off-by: Jeff King <peff@peff.net>
---
 usage.c | 6 ++++++
 1 file changed, 6 insertions(+)
diff --git a/usage.c b/usage.c
index b1cbe6799..ad6d2910f 100644
--- a/usage.c
+++ b/usage.c
@@ -12,7 +12,13 @@ void vreportf(const char *prefix, const char *err, va_list params)
 {
 	char msg[4096];
 	FILE *fh = error_handle ? error_handle : stderr;
+	char *p;
+
 	vsnprintf(msg, sizeof(msg), err, params);
+	for (p = msg; *p; p++) {
+		if (iscntrl(*p) && *p != '\t' && *p != '\n')
+			*p = '?';
+	}
 	fprintf(fh, "%s%s\n", prefix, msg);
 }
 
-- 
2.11.0.627.gfa6151259
Previous: Jeff KingNext: Jeff King
Message 3 of 6 in “sanitizing error message contents”
  1. 0/2 sanitizing error message contentsJeff King, Jan 11, 2017
  2. 1/2 Revert "vreportf: avoid intermediate buffer"Jeff King, Jan 11, 2017
  3. 2/2 vreport: sanitize ASCII control charsJeff King, Jan 11, 2017
  4. 3/2 vreportf: add prefix to each lineJeff King, Jan 11, 2017
  5. Junio C HamanoJan 11, 2017
  6. Jeff KingJan 12, 2017

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.