Re: BUG #17788: Incorrect memory access when parsing empty string as sql_standard interval
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: exclusion@gmail.com
Cc: pgsql-bugs@lists.postgresql.org
Date: 2023-02-12T17:53:39Z
Lists: pgsql-bugs
PG Bug reporting form <noreply@postgresql.org> writes: > When executing under valgrind: > SET IntervalStyle TO sql_standard; > SELECT ''::interval; > The following error is detected: > ==00:00:00:03.574 1155861== Use of uninitialised value of size 8 > ==00:00:00:03.574 1155861== at 0x606ADE: DecodeInterval > (datetime.c:3368) Good catch! For me, it dumps core about half the time even without using valgrind. > This defect was introduced by the commit e39f9904. > Before that commit the check > if (IntervalStyle == INTSTYLE_SQL_STANDARD && *field[0] == '-') > was guarded by > if (fmask == 0) > return DTERR_BAD_FORMAT; > but now field[0] is accessed unconditionally (even when nf == 0) for the > SQL_STANDARD style. Right. Not checking nf > 0 wasn't great style there in any case, but it accidentally failed to fail before. Fix pushed --- thanks for the report! regards, tom lane
Commits
-
Avoid dereferencing an undefined pointer in DecodeInterval().
- 5e80d3515488 16.0 landed
- 0ef65d0f55e5 15.3 landed
-
Fix overflow hazards in interval input and output conversions.
- e39f99046710 15.0 cited