aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gist.c
diff options
context:
space:
mode:
authorTomas Vondra <tomas.vondra@postgresql.org>2019-12-03 16:55:51 +0100
committerTomas Vondra <tomas.vondra@postgresql.org>2019-12-03 18:40:48 +0100
commita8a8c6b296406bbf30948768939c08457bd468a4 (patch)
tree9bddcc18396f149df35129eafa05de3e84895aa8 /src/backend/access/gist/gist.c
parentef30975b49702f9f8aaed7b1cd8f78470ed1b22d (diff)
downloadpostgresql-a8a8c6b296406bbf30948768939c08457bd468a4.tar.gz
postgresql-a8a8c6b296406bbf30948768939c08457bd468a4.zip
Ensure maxlen is at leat 1 in dict_int
The dict_int text search dictionary template accepts maxlen parameter, which is then used to cap the length of input strings. The value was not properly checked, and the code simply does txt[d->maxlen] = '\0'; to insert a terminator, leading to segfaults with negative values. This commit simply rejects values less than 1. The issue was there since dct_int was introduced in 9.3, so backpatch all the way back to 9.4 which is the oldest supported version. Reported-by: cili Discussion: https://postgr.es/m/16144-a36a5bef7657047d@postgresql.org Backpatch-through: 9.4
Diffstat (limited to 'src/backend/access/gist/gist.c')
0 files changed, 0 insertions, 0 deletions