linux-integrity.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Roberto Sassu <roberto.sassu@huawei.com>
Cc: Jeremy Boone <Jeremy.Boone@nccgroup.trust>,
	"linux-integrity@vger.kernel.org"
	<linux-integrity@vger.kernel.org>,
	James.Bottomley@HansenPartnership.com, tomas.winkler@intel.com
Subject: Re: EXTERNAL: [PATCH v2 2/3] tpm: modify tpm_pcr_read() definition to pass TPM hash algorithms
Date: Sun, 16 Sep 2018 15:30:47 +0300	[thread overview]
Message-ID: <20180916123047.GE5040@linux.intel.com> (raw)
In-Reply-To: <e1d77563-81fd-36f0-648f-3325969b05af@huawei.com>

On Wed, Sep 05, 2018 at 05:03:03PM +0200, Roberto Sassu wrote:
> On 9/5/2018 3:43 PM, Jeremy Boone wrote:
> > Some comments on tpm2_pcr_read below.
> > 
> > The tpm2_pcr_read function uses TPM2_ST_NO_SESSIONS. This means that the response payload is not integrity protected with an HMAC. If there is a man-in-the-middle sitting on the serial bus that connects the TPM peripheral to the processor, they can tamper with the response parameters.
> > 
> > In your changes to tpm2_pcr_read, the memcpy is now become a variable-length operation, instead of just copying a fixed number of bytes. If the MITM modifies the response field out->digest_size before it is received by the driver, they can make it a very large value, forcing a buffer overflow of the out->digest array.
> > 
> > Adding a session to the PCR Read command seems like overkill in this case. I wouldn't recommend that as a solution here.  So to fix this I would suggest simply checking the digest size before the memcpy.
> 
> Hi Jeremy
> 
> ok, thanks.
> 
> Roberto

Yeah, definitely not in the scope of this patch set. James Bottomley was
working on sessions at some point but I'm not sure if he is still
continuing that work or not.

In order to get sessions everywhere we would first need to get
everything to use struct tpm_buf. Tomas Winkler was working on a patch
set for this but that also somehow stagnated at some point.

/Jarkko

  parent reply	other threads:[~2018-09-16 17:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180905114202.7757-1-roberto.sassu@huawei.com>
     [not found] ` <20180905114202.7757-3-roberto.sassu@huawei.com>
2018-09-05 13:43   ` EXTERNAL: [PATCH v2 2/3] tpm: modify tpm_pcr_read() definition to pass TPM hash algorithms Jeremy Boone
     [not found]     ` <e1d77563-81fd-36f0-648f-3325969b05af@huawei.com>
2018-09-16 12:30       ` Jarkko Sakkinen [this message]
2018-09-16 12:37         ` Winkler, Tomas
2018-09-16 19:21           ` Jarkko Sakkinen
2018-09-26 14:09       ` Mimi Zohar
2018-09-26 14:39         ` Roberto Sassu
2018-09-10 18:42 ` [PATCH v2 0/3] tpm: retrieve digest size of unknown algorithms from TPM Jarkko Sakkinen
     [not found] ` <20180905114202.7757-2-roberto.sassu@huawei.com>
2018-09-16 12:13   ` [PATCH v2 1/3] tpm: rename and export tpm2_digest and tpm2_algorithms Jarkko Sakkinen
     [not found] ` <20180905114202.7757-4-roberto.sassu@huawei.com>
2018-09-16 12:37   ` [PATCH v2 3/3] tpm: retrieve digest size of unknown algorithms with PCR read Jarkko Sakkinen
2018-09-17 10:02     ` Roberto Sassu
2018-09-17 21:16       ` Jarkko Sakkinen
2018-09-18  7:14         ` Roberto Sassu
2018-09-18 18:54           ` Jarkko Sakkinen

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=20180916123047.GE5040@linux.intel.com \
    --to=jarkko.sakkinen@linux.intel.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=Jeremy.Boone@nccgroup.trust \
    --cc=linux-integrity@vger.kernel.org \
    --cc=roberto.sassu@huawei.com \
    --cc=tomas.winkler@intel.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;
as well as URLs for NNTP newsgroup(s).