aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2020-10-16 11:59:13 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2020-10-16 11:59:36 -0400
commit1eb2d7e3ea8ef683d29b4f0a81b6f21662edd1e7 (patch)
tree239fdee26941a9ce0ef28fc2c911f889c876dd6a
parentb1452f5c09f055e8511fdcaf26c7b267cbbf6b4f (diff)
downloadpostgresql-1eb2d7e3ea8ef683d29b4f0a81b6f21662edd1e7.tar.gz
postgresql-1eb2d7e3ea8ef683d29b4f0a81b6f21662edd1e7.zip
Add missing error check in pgcrypto/crypt-md5.c.
In theory, the second px_find_digest call in px_crypt_md5 could fail even though the first one succeeded, since resource allocation is required. Don't skip testing for a failure. (If one did happen, the likely result would be a crash rather than clean recovery from an OOM failure.) The code's been like this all along, so back-patch to all supported branches. Daniel Gustafsson Discussion: https://postgr.es/m/AA8D6FE9-4AB2-41B4-98CB-AE64BA668C03@yesql.se
-rw-r--r--contrib/pgcrypto/crypt-md5.c8
1 files changed, 7 insertions, 1 deletions
diff --git a/contrib/pgcrypto/crypt-md5.c b/contrib/pgcrypto/crypt-md5.c
index 6a09d76989f..cb1b97d7786 100644
--- a/contrib/pgcrypto/crypt-md5.c
+++ b/contrib/pgcrypto/crypt-md5.c
@@ -65,11 +65,17 @@ px_crypt_md5(const char *pw, const char *salt, char *passwd, unsigned dstlen)
/* get the length of the true salt */
sl = ep - sp;
- /* */
+ /* we need two PX_MD objects */
err = px_find_digest("md5", &ctx);
if (err)
return NULL;
err = px_find_digest("md5", &ctx1);
+ if (err)
+ {
+ /* this path is possible under low-memory circumstances */
+ px_md_free(ctx);
+ return NULL;
+ }
/* The password first, since that is what is most unknown */
px_md_update(ctx, (const uint8 *) pw, strlen(pw));