From: Lukasz Pawelczyk <l.pawelczyk@samsung.com>
Date: Fri, 17 Nov 2017 10:32:26 +0000 (+0100)
Subject: Fix possible segfault in seal_initialize
X-Git-Tag: submit/tizen/20180315.113946~3
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=refs%2Fchanges%2F71%2F160671%2F1;p=platform%2Fcore%2Fsecurity%2Fyaca.git

Fix possible segfault in seal_initialize

The iv is not mandatory. It depends on bcm mode and is already checked
in this function. Don't blindly write to *iv because in some cases it
might be NULL.

Change-Id: Ieddf81b77482d2aec49d1cde3291c08d702b7c43
---

diff --git a/src/seal.c b/src/seal.c
index a7c3b50..24188e4 100644
--- a/src/seal.c
+++ b/src/seal.c
@@ -188,8 +188,11 @@ API int yaca_seal_initialize(yaca_context_h *ctx,
 
 	*sym_key = lenc_sym_key;
 	lenc_sym_key = YACA_KEY_NULL;
-	*iv = liv;
-	liv = YACA_KEY_NULL;
+	if (iv != NULL) {
+		*iv = liv;
+		liv = YACA_KEY_NULL;
+	}
+
 	ret = YACA_ERROR_NONE;
 
 exit: