pgsql: Fix memory leak when rejecting bogus DH parameters. - Mailing list pgsql-committers

From Tom Lane
Subject pgsql: Fix memory leak when rejecting bogus DH parameters.
Date
Msg-id E1lNelj-0004vk-18@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Fix memory leak when rejecting bogus DH parameters.

While back-patching e0e569e1d, I noted that there were some other
places where we ought to be applying DH_free(); namely, where we
load some DH parameters from a file and then reject them as not
being sufficiently secure.  While it seems really unlikely that
anybody would hit these code paths in production, let alone do
so repeatedly, let's fix it for consistency.

Back-patch to v10 where this code was introduced.

Discussion: https://postgr.es/m/16160-18367e56e9a28264@postgresql.org

Branch
------
REL_10_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/ad6c19066d931c66612531d83b15dfd2464e2a29

Modified Files
--------------
src/backend/libpq/be-secure-openssl.c | 3 +++
1 file changed, 3 insertions(+)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Fix memory leak when rejecting bogus DH parameters.
Next
From: Tom Lane
Date:
Subject: pgsql: Fix up pg_dump's handling of per-attribute compression options.