From: "Erik Elfström" <erik.elfstrom@gmail.com>
To: git@vger.kernel.org
Cc: "Erik Elfström" <erik.elfstrom@gmail.com>
Subject: [PATCH v6 3/7] setup: sanity check file size in read_gitfile_gently
Date: Sun, 10 May 2015 22:00:37 +0200 [thread overview]
Message-ID: <1431288041-21077-4-git-send-email-erik.elfstrom@gmail.com> (raw)
In-Reply-To: <1431288041-21077-1-git-send-email-erik.elfstrom@gmail.com>
read_gitfile_gently will allocate a buffer to fit the entire file that
should be read. Add a sanity check of the file size before opening to
avoid allocating a potentially huge amount of memory if we come across
a large file that someone happened to name ".git". The limit is set to
a sufficiently unreasonable size that should never be exceeded by a
genuine .git file.
Signed-off-by: Erik Elfström <erik.elfstrom@gmail.com>
---
cache.h | 1 +
setup.c | 8 ++++++++
2 files changed, 9 insertions(+)
diff --git a/cache.h b/cache.h
index 54c902b..7c8abcb 100644
--- a/cache.h
+++ b/cache.h
@@ -452,6 +452,7 @@ extern const char *get_git_work_tree(void);
#define READ_GITFILE_ERR_NO_PATH 6
#define READ_GITFILE_ERR_CANT_VERIFY_PATH 7
#define READ_GITFILE_ERR_NOT_A_REPO 8
+#define READ_GITFILE_ERR_TOO_LARGE 9
extern const char *read_gitfile_gently(const char *path, int *return_error_code);
#define read_gitfile(path) read_gitfile_gently((path), NULL)
extern const char *resolve_gitdir(const char *suspect);
diff --git a/setup.c b/setup.c
index b919ea6..bfaf4a6 100644
--- a/setup.c
+++ b/setup.c
@@ -381,6 +381,7 @@ static int check_repository_format_gently(const char *gitdir, int *nongit_ok)
*/
const char *read_gitfile_gently(const char *path, int *return_error_code)
{
+ static const int one_MB = 1 << 20;
int error_code = 0;
char *buf = NULL;
char *dir = NULL;
@@ -404,6 +405,11 @@ const char *read_gitfile_gently(const char *path, int *return_error_code)
error_code = READ_GITFILE_ERR_OPEN_FAILED;
goto cleanup_return;
}
+ if (st.st_size > one_MB) {
+ close(fd);
+ error_code = READ_GITFILE_ERR_TOO_LARGE;
+ goto cleanup_return;
+ }
buf = xmalloc(st.st_size + 1);
len = read_in_full(fd, buf, st.st_size);
close(fd);
@@ -463,6 +469,8 @@ cleanup_return:
return NULL;
case READ_GITFILE_ERR_OPEN_FAILED:
die_errno("Error opening '%s'", path);
+ case READ_GITFILE_ERR_TOO_LARGE:
+ die("Too large to be a .git file: '%s'", path);
case READ_GITFILE_ERR_READ_FAILED:
die("Error reading %s", path);
case READ_GITFILE_ERR_INVALID_FORMAT:
--
2.4.0.60.gf7143f7
next prev parent reply other threads:[~2015-05-10 20:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-10 20:00 [PATCH v6 0/7] Improving performance of git clean Erik Elfström
2015-05-10 20:00 ` [PATCH v6 1/7] setup: add gentle version of is_git_directory Erik Elfström
2015-05-10 20:00 ` [PATCH v6 2/7] setup: add gentle version of read_gitfile Erik Elfström
2015-05-10 20:00 ` Erik Elfström [this message]
2015-05-12 6:46 ` [PATCH v6 3/7] setup: sanity check file size in read_gitfile_gently erik elfström
2015-05-10 20:00 ` [PATCH v6 4/7] t7300: add tests to document behavior of clean and nested git Erik Elfström
2015-05-10 20:00 ` [PATCH v6 5/7] p7300: add performance tests for clean Erik Elfström
2015-05-10 20:00 ` [PATCH v6 6/7] clean: improve performance when removing lots of directories Erik Elfström
2015-05-10 20:00 ` [PATCH v6 7/7] RFC: Change error handling scheme in read_gitfile_gently Erik Elfström
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1431288041-21077-4-git-send-email-erik.elfstrom@gmail.com \
--to=erik.elfstrom@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).