pgsql: Fix possible buffer overrun in hba.c.

From: Thomas Munro <tmunro(at)postgresql(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Fix possible buffer overrun in hba.c.
Date: 2018-11-13 03:36:07
Message-ID: E1gMPUl-0006CL-M2@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Fix possible buffer overrun in hba.c.

Coverty reports a possible buffer overrun in the code that populates the
pg_hba_file_rules view. It may not be a live bug due to restrictions
on options that can be used together, but let's increase MAX_HBA_OPTIONS
and correct a nearby misleading comment.

Back-patch to 10 where this code arrived.

Reported-by: Julian Hsiao
Discussion: https://postgr.es/m/CADnGQpzbkWdKS2YHNifwAvX5VEsJ5gW49U4o-7UL5pzyTv4vTg%40mail.gmail.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/6a3dcd28568a04b6e4aea2bf41ea2c7e9c7b0e96

Modified Files
--------------
src/backend/libpq/hba.c | 9 ++++++---
1 file changed, 6 insertions(+), 3 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Thomas Munro 2018-11-13 03:37:09 pgsql: Fix possible buffer overrun in hba.c.
Previous Message Michael Paquier 2018-11-13 00:04:38 pgsql: Remove CommandCounterIncrement() after processing ON COMMIT DELE