summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRichard Levitte <levitte@openssl.org>2023-01-10 08:27:44 +0100
committerRichard Levitte <levitte@openssl.org>2023-01-11 23:38:13 +0100
commitc455f87aebf245814ba58d6a398b45ca4e80d1d7 (patch)
tree1fb247da2e81772ef8de05cb70997b0acfcbd5a7
parentc2ae89148343750e420b72ef1b709ebbc16e47b8 (diff)
OSSL_PARAM_BLD and BIGNUM; ensure at least one byte is allocated
A zero BIGNUM contains zero bytes, while OSSL_PARAMs with an INTEGER (or UNSIGNED INTEGER) data type are expected to have at least one data byte allocated, containing a zero. This wasn't handled correctly. Fixes #20011 Reviewed-by: Paul Dale <pauli@openssl.org> Reviewed-by: Tomas Mraz <tomas@openssl.org> (Merged from https://github.com/openssl/openssl/pull/20013)
-rw-r--r--crypto/param_build.c4
1 files changed, 4 insertions, 0 deletions
diff --git a/crypto/param_build.c b/crypto/param_build.c
index f00c0aa809..ae215ff5aa 100644
--- a/crypto/param_build.c
+++ b/crypto/param_build.c
@@ -218,6 +218,10 @@ static int push_BN(OSSL_PARAM_BLD *bld, const char *key,
}
if (BN_get_flags(bn, BN_FLG_SECURE) == BN_FLG_SECURE)
secure = 1;
+
+ /* The BIGNUM is zero, we must transfer at least one byte */
+ if (sz == 0)
+ sz++;
}
pd = param_push(bld, key, sz, sz, type, secure);
if (pd == NULL)