Re: Insufficient memory access checks in pglz_decompress

Поиск
Список
Период
Сортировка
От Flavien GUEDEZ
Тема Re: Insufficient memory access checks in pglz_decompress
Дата
Msg-id bb74b9f4-65c1-4d89-af20-7de623948e36@oopacity.net
обсуждение исходный текст
Ответ на Re: Insufficient memory access checks in pglz_decompress  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: Insufficient memory access checks in pglz_decompress  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-bugs
Thanks for your feedback, you are definitely right, I did not notice 
that (dp - off) was staying the same in the while loop.
Here is another much smaller patch.

Flavien


Le 18/10/2023 à 17:14, Tom Lane a écrit :
> Flavien GUEDEZ <flav.pg@oopacity.net> writes:
>> After some investigations about very corrupted toast data in one
>> postgres instance, I found that the pglz_decompress function (in
>> common/pg_lzcompress.c) does not check correctly where it copies data
>> from using memcpy(), which could result in segfault.
>> In this function, there are other checks to ensure that we do not copy
>> after the destination end, but not if we copy data from "before the
>> beginning".
> Hmm, would it not be better to add this check to the existing "Check for
> corrupt data" a bit further up?  Then you'd only need one instance of
> the test, and only need to do it once per tag (note the comment pointing
> out that dp - off stays the same), and overall it'd be less surprising IMO.
>
>             regards, tom lane

Вложения

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Insufficient memory access checks in pglz_decompress
Следующее
От: PG Bug reporting form
Дата:
Сообщение: BUG #18160: first create table show "ERROR: permission denied for schema public", next create table works