From nobody Fri May 3 17:56:03 2024 Delivered-To: importer@patchew.org Received-SPF: pass (zohomail.com: domain of groups.io designates 66.175.222.12 as permitted sender) client-ip=66.175.222.12; envelope-from=bounce+27952+63688+1787277+3901457@groups.io; helo=web01.groups.io; Authentication-Results: mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of groups.io designates 66.175.222.12 as permitted sender) smtp.mailfrom=bounce+27952+63688+1787277+3901457@groups.io; dmarc=fail(p=none dis=none) header.from=intel.com ARC-Seal: i=1; a=rsa-sha256; t=1596505444; cv=none; d=zohomail.com; s=zohoarc; b=e3tEzITQhDvGauWcPrN7Vu5T4JlJI+j3O82b7anY030zvNvIeBHaSHiRKDF59bOpjNLBF7N8AfkItSrGhAzd9+CPkJZAKVHMdWj5yqb7CBd2iPlrKv86G6XMA7AU6kkBLCAojj3LhKfZ1UhLLTYgXtBI6SOAcxR2qaeodf2AwRc= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1596505444; h=Content-Transfer-Encoding:Cc:Date:From:List-Id:List-Unsubscribe:MIME-Version:Message-ID:Reply-To:Sender:Subject:To; bh=Nh5BLtK7oXCQf629CkJz3tYx1SOpepdI74m9qYo6pDI=; b=e9l+qhkLYj3wLmhnnecjckJyGx/qaBpBzinI2pjsOFMwmN0905OfwO0DQk+jlj9+LILD4CAihqQDn6Q6qh/BW7qBUfaTO3UdlT7Cw+KkETpS3mKohBMCCZS/IVRn1CYTwy8dY7hcbAySzJ14Saq6NVNJ5fXYFSL+7EC1rt4OrV0= ARC-Authentication-Results: i=1; mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of groups.io designates 66.175.222.12 as permitted sender) smtp.mailfrom=bounce+27952+63688+1787277+3901457@groups.io; dmarc=fail header.from= (p=none dis=none) header.from= Received: from web01.groups.io (web01.groups.io [66.175.222.12]) by mx.zohomail.com with SMTPS id 1596505444716988.4958458225677; Mon, 3 Aug 2020 18:44:04 -0700 (PDT) Return-Path: X-Received: by 127.0.0.2 with SMTP id vZDvYY1788612xiJW4XNSsl1; Mon, 03 Aug 2020 18:44:04 -0700 X-Received: from mga17.intel.com (mga17.intel.com [192.55.52.151]) by mx.groups.io with SMTP id smtpd.web12.10681.1596505443366998598 for ; Mon, 03 Aug 2020 18:44:03 -0700 IronPort-SDR: 0RAmAOl02M6zhq5owCzpsiqU0xturrA2zn3/Eu3oalcNF6hZooHzBn9J6azRTkVJyYG4si27vd kFUyaluTT+6w== X-IronPort-AV: E=McAfee;i="6000,8403,9702"; a="132293074" X-IronPort-AV: E=Sophos;i="5.75,432,1589266800"; d="scan'208";a="132293074" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False X-Received: from orsmga007.jf.intel.com ([10.7.209.58]) by fmsmga107.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 03 Aug 2020 18:44:02 -0700 IronPort-SDR: lQF/yq/4kLNyDoXL9JVxpSZkqjdWvkD0nrc2iq0V2PGTvNlTqRGc/L0+7IXWtHVjbNm5MalRza f5ZYpR7Kh7tQ== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.75,432,1589266800"; d="scan'208";a="332306578" X-Received: from guominji-mobl.ccr.corp.intel.com ([10.238.13.140]) by orsmga007.jf.intel.com with ESMTP; 03 Aug 2020 18:44:01 -0700 From: "Guomin Jiang" To: devel@edk2.groups.io Cc: Jian J Wang , Liming Gao Subject: [edk2-devel] [edk2-wiki][PATCH] Update the Boot Guard TOCTOU wiki page. Date: Tue, 4 Aug 2020 09:44:00 +0800 Message-Id: <20200804014400.1274-1-guomin.jiang@intel.com> MIME-Version: 1.0 Precedence: Bulk List-Unsubscribe: Sender: devel@edk2.groups.io List-Id: Mailing-List: list devel@edk2.groups.io; contact devel+owner@edk2.groups.io Reply-To: devel@edk2.groups.io,guomin.jiang@intel.com X-Gm-Message-State: jsq8353KxNQxAX3MFVbfHy95x1787277AA= Content-Transfer-Encoding: quoted-printable DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=groups.io; q=dns/txt; s=20140610; t=1596505444; bh=uWZRscMnzEWUKrHQIhKOONYmEOnKTWMzU1n92iqXwG4=; h=Cc:Date:From:Reply-To:Subject:To; b=g5olbCM1/cFORqVLXgggWqL34gMhCGjb0wZ3vYD9/tXKooC05v74s3ZTa1ASiEiLcq7 VPk8Zg1wFl4HP8XqNrR8FrCQ7cpTC6vzyGc+XQ2lcef3L9h+gq+bxf2YDbQp5dIKmNkxu yJfPoAoYHxIHO1tdWLrF3XuXt0VkrVg7TjA= X-ZohoMail-DKIM: pass (identity @groups.io) Content-Type: text/plain; charset="utf-8" The Boot Guard TOCTOU have been migrated into edk2/master. Update the document to meet the change. Signed-off-by: Guomin Jiang Cc: Jian J Wang Cc: Liming Gao Reviewed-by: Jian J Wang --- Boot-Guard-TOCTOU-Vulnerability-Mitigation.md | 28 ++++++------------- 1 file changed, 8 insertions(+), 20 deletions(-) diff --git a/Boot-Guard-TOCTOU-Vulnerability-Mitigation.md b/Boot-Guard-TOC= TOU-Vulnerability-Mitigation.md index e59c7b1..5e0c856 100644 --- a/Boot-Guard-TOCTOU-Vulnerability-Mitigation.md +++ b/Boot-Guard-TOCTOU-Vulnerability-Mitigation.md @@ -45,32 +45,20 @@ references must be updated. In this mitigation, the pro= cess of performing these The changes described in this mitigation are intended to simply integrate = into firmware solutions. For the changes to function as intended, the platform firmware implementation should follow t= hese guidelines. =20 -The changes are currently being staged in the following EDK II fork for ad= ditional validation before being -sent to the EDK II mailing list: https://github.com/makubacki/edk2/tree/bt= g_toctou_mitigation_staging - -The changes should not be considered final or production ready until they = are reviewed and pushed onto edk2/master. - -1. Always ensure PcdShadowPeimOnBoot and PcdShadowPeimOnS3Boot - (if platform supports S3) are set to TRUE if Boot Guard is - enabled and V=3D1 or M=3D1. -2. Always ensure PcdMigrateTemporaryRamFirmwareVolumes is set to TRUE. -3. Ensure that all PEIMs are relocatable. Relocation tables should +1. Always ensure PcdMigrateTemporaryRamFirmwareVolumes are set to TRUE + if Boot Guard is enabled and V=3D1 or M=3D1. +2. Ensure that all PEIMs are relocatable. Relocation tables should not be stripped. -4. If an Intel® Firmware Support Package (FSP) binary solution is +3. If an Intel® Firmware Support Package (FSP) binary solution is used, the binary must have these mitigation changes integrated. -5. Avoid maintaining pointers to pre-memory addresses inside embedded +4. Avoid maintaining pointers to pre-memory addresses inside embedded structures or other non-standard structures that the automatic migration code introduced in this change cannot identify. -6. Migrate the FIT table based on platform requirements for FIT +5. Migrate the FIT table based on platform requirements for FIT access in post-memory. =20 -**Very Important** - -7. Enable paging after memory initialization and mark the IBB range - as Not Present (NP). - - This will cause a page fault on access to the IBB region. This CR2 regi= ster can be used to identify the address - accessed and the IP. +Notes: IBB will be set Not Present, you will see a page fault if any code = access to the IBB region after migration. + the address where the code access can be identified in the CR2 regi= ster. =20 # High-Level Migration Required Resources that must be migrated can be categorized as code or data. --=20 2.25.1.windows.1 -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#63688): https://edk2.groups.io/g/devel/message/63688 Mute This Topic: https://groups.io/mt/75979644/1787277 Group Owner: devel+owner@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [importer@patchew.org] -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-