Linux Integrity Measurement development
 help / color / mirror / Atom feed
From: samasth.norway.ananda@oracle.com
To: Mimi Zohar <zohar@linux.ibm.com>,
	roberto.sassu@huawei.com, dmitry.kasatkin@gmail.com
Cc: eric.snowberg@oracle.com, linux-integrity@vger.kernel.org
Subject: Re: [PATCH ] ima: fix buffer overrun in ima_eventdigest_init_common
Date: Fri, 21 Jun 2024 15:56:33 -0700	[thread overview]
Message-ID: <f5476da1-08c4-4c04-8e59-588688de9b83@oracle.com> (raw)
In-Reply-To: <e667feaa37e186a2a240ca70c994c27e88724876.camel@linux.ibm.com>



On 6/21/24 3:44 PM, Mimi Zohar wrote:
> Hi Samasth,
> 
> On Thu, 2024-06-20 at 12:46 -0700, Samasth Norway Ananda wrote:
>> Function ima_eventdigest_init() can call ima_eventdigest_init_common()
>> with HASH_ALGO__LAST which is then used to access the array
>> hash_digest_size[] leading to buffer overrun. Have a conditional
>> statement to handle this.
> 
> The original 'ima' template ("d|n") digest is not prefixed with the digest
> algorithm, since it is hard coded to sha1.  ima_eventdigest_init() intentionally
> calls ima_eventdigest_init_common() with HASH_ALGO__LAST.  To avoid ...
> 
>>
>> Fixes: 9fab303a2cb3 ("ima: fix violation measurement list record")
>> Signed-off-by: Samasth Norway Ananda <samasth.norway.ananda@oracle.com>
>> ---
>>   security/integrity/ima/ima_template_lib.c | 8 ++++++--
>>   1 file changed, 6 insertions(+), 2 deletions(-)
>>
>> diff --git a/security/integrity/ima/ima_template_lib.c b/security/integrity/ima/ima_template_lib.c
>> index 4183956c53af..14c000fe8312 100644
>> --- a/security/integrity/ima/ima_template_lib.c
>> +++ b/security/integrity/ima/ima_template_lib.c
>> @@ -320,13 +320,17 @@ static int ima_eventdigest_init_common(const u8 *digest, u32 digestsize,
>>   
>>   	if (digest)
> 
> Please add a brace after "digest" and before "else".
> 
> Refer to the section titled "3) Placing Braces and Spaces" in "
> https://www.kernel.org/doc/html/v4.10/process/coding-style.html.
> 
> 
>>   		memcpy(buffer + offset, digest, digestsize);
>> -	else
>> +	else {
>>   		/*
>>   		 * If digest is NULL, the event being recorded is a violation.
>>   		 * Make room for the digest by increasing the offset by the
>>   		 * hash algorithm digest size.
>>   		 */
> 
> Please update the comment to reflect the case when the hash algorithm isn't
> specified.
> 
>> -		offset += hash_digest_size[hash_algo];
>> +		if (hash_algo < HASH_ALGO__LAST)
>> +                        offset += hash_digest_size[hash_algo];
>> +               else
>> +                        offset += IMA_DIGEST_SIZE;
>> +	}
>>   
>>   	return ima_write_template_field_data(buffer, offset + digestsize,
>>   					     fmt, field_data);
> 
> Please fix the other scripts/checkpatch.pl complaints.

Thanks for correcting me Mimi. I should have checked that before 
sending. I will make the changes and send a v2 of the patch.

> 
> thanks,
> 
> Mimi
> 

      reply	other threads:[~2024-06-21 22:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-20 19:46 [PATCH ] ima: fix buffer overrun in ima_eventdigest_init_common Samasth Norway Ananda
2024-06-21 18:11 ` Enrico Bravi
2024-06-21 22:44 ` Mimi Zohar
2024-06-21 22:56   ` samasth.norway.ananda [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f5476da1-08c4-4c04-8e59-588688de9b83@oracle.com \
    --to=samasth.norway.ananda@oracle.com \
    --cc=dmitry.kasatkin@gmail.com \
    --cc=eric.snowberg@oracle.com \
    --cc=linux-integrity@vger.kernel.org \
    --cc=roberto.sassu@huawei.com \
    --cc=zohar@linux.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox