From nobody Tue Apr 30 16:29:36 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+63950+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+63950+1787277+3901457@groups.io; dmarc=fail(p=none dis=none) header.from=intel.com ARC-Seal: i=1; a=rsa-sha256; t=1597124055; cv=none; d=zohomail.com; s=zohoarc; b=noyqFxsp0f9sSkVO+f0C3bhij7ui7vUWImqRoSWDQ3c+tXTo+5oZwErjnNKxJs8KyxhRfqRhnETz48FJlTilAoT9kZePUaEQfs9q892qxHuwYNNIwhd852ZHTeBCHiJx4aIHFSI97xgMiiegmCnuilnszjbS8hWpziyu+rUCpSM= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1597124055; h=Content-Transfer-Encoding:Cc:Date:From:List-Id:List-Unsubscribe:MIME-Version:Message-ID:Reply-To:Sender:Subject:To; bh=VNaJbjLLgMTOIZAv4OUorphF5+Y8wXpWW96mH7f3Peg=; b=EbqHxTnPH/5UwyzX3+tt1eKWMsE2OFQ3WZ30HzcCDauz8AbqHpiJNXl1zlrDrGoUtwp+H1EJZlKAEeIOdxkgq3rW8NcKMpfEraruFA7/fxqvtUVnjd1tsqZbvobKlKS8EDyRAlTst57an2D8iAGTtTcdRQiEAwg9va1m7v22b/A= 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+63950+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 1597124055185861.8801156924233; Mon, 10 Aug 2020 22:34:15 -0700 (PDT) Return-Path: X-Received: by 127.0.0.2 with SMTP id tAZGYY1788612xzDoWTZ4Mke; Mon, 10 Aug 2020 22:34:14 -0700 X-Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by mx.groups.io with SMTP id smtpd.web10.9111.1597124053529204379 for ; Mon, 10 Aug 2020 22:34:13 -0700 IronPort-SDR: xeCJMk3BCk6SR035VrC2UhlunkJWk4CP0/IKpNhh0wWZFx7ycTlDyw1quVWIy1Px+JO9iMYBY4 ANURDk7Wgkmg== X-IronPort-AV: E=McAfee;i="6000,8403,9709"; a="151348951" X-IronPort-AV: E=Sophos;i="5.75,459,1589266800"; d="scan'208";a="151348951" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False X-Received: from orsmga008.jf.intel.com ([10.7.209.65]) by fmsmga102.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 10 Aug 2020 22:34:12 -0700 IronPort-SDR: zjrG/GzQCftGk11AnLPI3c6JNyZ4ebbvggK2+42CKuObYT+pVMpXZRuMlo6jmndQ+cnsfqHcL2 LwMxuxdFFThw== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.75,459,1589266800"; d="scan'208";a="324662667" X-Received: from guominji-mobl.ccr.corp.intel.com ([10.238.13.140]) by orsmga008.jf.intel.com with ESMTP; 10 Aug 2020 22:34:11 -0700 From: "Guomin Jiang" To: devel@edk2.groups.io Cc: Jian J Wang , Liming Gao Subject: [edk2-devel] [edk2-wiki][PATCH v2] Update the Boot Guard TOCTOU wiki page. Date: Tue, 11 Aug 2020 13:32:25 +0800 Message-Id: <20200811053225.1277-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: fTkiuRrVFusLsHeYS4ysmnv4x1787277AA= Content-Transfer-Encoding: quoted-printable DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=groups.io; q=dns/txt; s=20140610; t=1597124054; bh=3KXflgYMrnNtwn6DB14NEi/+e9l4nCEyvLu3UsbiGiE=; h=Cc:Date:From:Reply-To:Subject:To; b=fqF2c2NXQCML5WTYUl7zoSdENTNkKOoa4rDc/bMT0CVZIZkofXbV0U4o6Fi4/ZuBRBe 2jkLSCogGkPFU6QlRHR2LQgaCr7I/zrcLyzxWwW0vsNuwOEm3gfKqz5wLQsBltWtSsNEq 3H9fgZW0k26euNDnlaDddrSC23Lviffg80k= 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..64b9d66 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 is 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 (#63950): https://edk2.groups.io/g/devel/message/63950 Mute This Topic: https://groups.io/mt/76120928/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-