File openssl-CVE-2016-2106.patch of Package openssl.4105
From 3e17fe7e40ed2eeb4f0892d376ac40d279780aa9 Mon Sep 17 00:00:00 2001
From: Matt Caswell <firstname.lastname@example.org>
Date: Thu, 3 Mar 2016 23:36:23 +0000
Subject: [PATCH] Fix encrypt overflow
An overflow can occur in the EVP_EncryptUpdate function. If an attacker is
able to supply very large amounts of input data after a previous call to
EVP_EncryptUpdate with a partial block then a length check can overflow
resulting in a heap corruption.
Following an analysis of all OpenSSL internal usage of the
EVP_EncryptUpdate function all usage is one of two forms.
The first form is like this:
i.e. where the EVP_EncryptUpdate() call is known to be the first called
function after an EVP_EncryptInit(), and therefore that specific call
must be safe.
The second form is where the length passed to EVP_EncryptUpdate() can be
seen from the code to be some small value and therefore there is no
possibility of an overflow.
Since all instances are one of these two forms, I believe that there can
be no overflows in internal code due to this problem.
It should be noted that EVP_DecryptUpdate() can call EVP_EncryptUpdate()
in certain code paths. Also EVP_CipherUpdate() is a synonym for
EVP_EncryptUpdate(). Therefore I have checked all instances of these
calls too, and came to the same conclusion, i.e. there are no instances
in internal usage where an overflow could occur.
This could still represent a security issue for end user code that calls
this function directly.
Issue reported by Guido Vranken.
crypto/evp/evp_enc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- openssl-1.0.1i.orig/crypto/evp/evp_enc.c 2016-04-28 16:39:03.977366307 +0200
+++ openssl-1.0.1i/crypto/evp/evp_enc.c 2016-04-28 16:40:19.449640518 +0200
@@ -400,7 +400,7 @@ int EVP_EncryptUpdate(EVP_CIPHER_CTX *ct
OPENSSL_assert(bl <= (int)sizeof(ctx->buf));
if (i != 0)
- if (i+inl < bl)
+ if (bl - i > inl)