pgsql: Fix strsep() use for SCRAM secrets parsing - Mailing list pgsql-committers

From Peter Eisentraut
Subject pgsql: Fix strsep() use for SCRAM secrets parsing
Date
Msg-id E1t1jFG-001MBH-GF@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Fix strsep() use for SCRAM secrets parsing

The previous code (from commit 5d2e1cc117b) did not detect end of
string correctly, so it would fail to error out if fewer than the
expected number of fields were present, which could then later lead to
a crash when NULL string pointers are accessed.

Reported-by: Alexander Lakhin <exclusion@gmail.com>
Reported-by: Ranier Vilela <ranier.vf@gmail.com>
Discussion: https://www.postgresql.org/message-id/flat/79692bf9-17d3-41e6-b9c9-fc8c3944222a@eisentraut.org

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/24a36f91e32d6cbb8182c4cc6529d6e47587c988

Modified Files
--------------
src/backend/libpq/auth-scram.c | 12 ++++++++----
1 file changed, 8 insertions(+), 4 deletions(-)


pgsql-committers by date:

Previous
From: Fujii Masao
Date:
Subject: pgsql: Remove unused code for unlogged materialized views.
Next
From: Peter Eisentraut
Date:
Subject: pgsql: Fix memory leaks from incorrect strsep() uses