Re: BUG #18614: [ECPG] out of bound in DecodeDateTime

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: p(dot)nekrasov(at)fobos-nt(dot)ru, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18614: [ECPG] out of bound in DecodeDateTime
Date: 2024-10-16 00:18:10
Message-ID: Zw8GQrLHlgJlz3Qc@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, Oct 14, 2024 at 05:52:59PM -0400, Bruce Momjian wrote:
> /*
> - * check for valid day of month, now that we know for sure the month
> + * check for valid day of month and month, now that we know for sure the month
> * and year...
> */
> - if (tm->tm_mday < 1 || tm->tm_mday > day_tab[isleap(tm->tm_year)][tm->tm_mon - 1])
> + if (tm->tm_mon < 1 || tm->tm_mday < 1 || tm->tm_mday > day_tab[isleap(tm->tm_year)][tm->tm_mon - 1])
> return -1;

I would suggest adding a test. This is tricky enough and really easy
to miss, even if ECPG is not that touched these days.

There are a lot of callers of PGTYPEStimestamp_from_asc() in
dt_test.pgc that do sanity checks on such inputs.
--
Michael

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Paquier 2024-10-16 00:19:31 Re: BUG #18657: Using JSON_OBJECTAGG with volatile function leads to segfault
Previous Message Alena Rybakina 2024-10-15 23:21:09 Re: Performance Issue on Query 18 of TPC-H Benchmark