cache-tree: detect mismatching number of index entries
In t4058 we have some tests that exercise git-read-tree(1) when used with a tree that contains duplicate entries. While the expectation is that we fail, we ideally should fail gracefully without a segfault. But that is not the case: we never check that the number of entries in the cache-tree is less than or equal to the number of entries in the index. This can lead to an out-of-bounds read as we unconditionally access `istate->cache[idx]`, where `idx` is controlled by the number of cache-tree entries and the current position therein. The result is a segfault. Fix this segfault by adding a sanity check for the number of index entries before dereferencing them. Signed-off-by: Patrick Steinhardt <ps@pks.im> Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:

committed by
Junio C Hamano

parent
9f119599a6
commit
2be7fc012e
@ -933,6 +933,11 @@ static int verify_one(struct repository *r,
|
||||
pos = 0;
|
||||
}
|
||||
|
||||
if (it->entry_count + pos > istate->cache_nr) {
|
||||
ret = error(_("corrupted cache-tree has entries not present in index"));
|
||||
goto out;
|
||||
}
|
||||
|
||||
i = 0;
|
||||
while (i < it->entry_count) {
|
||||
struct cache_entry *ce = istate->cache[pos + i];
|
||||
|
Reference in New Issue
Block a user