From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, jian.j.wang@intel.com
Cc: Jiewen Yao <jiewen.yao@intel.com>, Chao Zhang <chao.b.zhang@intel.com>
Subject: Re: [edk2-devel] [PATCH v2 00/10] Fix false negative issue in DxeImageVerificationHandler
Date: Mon, 17 Feb 2020 08:48:51 +0100 [thread overview]
Message-ID: <9c8b47c7-765a-6064-49c3-a0a9578ccba6@redhat.com> (raw)
In-Reply-To: <20200214072745.1570-1-jian.j.wang@intel.com>
On 02/14/20 08:27, Wang, Jian J wrote:
>> v2 changes:
>> - Change IsCertHashFoundInDatabase to IsCertHashFoundInDbx (patch 10)
>> - Update result handling to all calling to IsCertHashFoundInDatabase
>> to be consistent (patch 6)
>> - Fix commit message and title length issue caught by PatchCheck tool
>
> REF: https://bugzilla.tianocore.org/show_bug.cgi?id=1608
> Patch branch: https://github.com/jwang36/edk2/tree/fix-bz1608-bypass-blacklist-check-via-signature-v2
>
> Cc: Jiewen Yao <jiewen.yao@intel.com>
> Cc: Chao Zhang <chao.b.zhang@intel.com>
>
> Jian J Wang (9):
> SecurityPkg/DxeImageVerificationLib: Fix memory leaks(CVE-2019-14575)
> SecurityPkg/DxeImageVerificationLib: reject CertStack.CertNumber==0
> per DBX(CVE-2019-14575)
> SecurityPkg/DxeImageVerificationLib: fix wrong fetch dbx in
> IsAllowedByDb(CVE-2019-14575)
> SecurityPkg/DxeImageVerificationLib: avoid bypass in fetching
> dbx(CVE-2019-14575)
> SecurityPkg/DxeImageVerificationLib: refactor db/dbx fetching
> code(CVE-2019-14575)
> SecurityPkg/DxeImageVerificationLib: Differentiate error/search result
> (1)(CVE-2019-14575)
> SecurityPkg/DxeImageVerificationLib: tighten default
> result(CVE-2019-14575)
> SecurityPkg/DxeImageVerificationLib: Differentiate error/search result
> (2)(CVE-2019-14575)
> SecurityPkg/DxeImageVerificationLib: change IsCertHashFoundInDatabase
> name(CVE-2019-14575)
>
> Laszlo Ersek (1):
> SecurityPkg/DxeImageVerificationLib: plug Data leak in
> IsForbiddenByDbx()(CVE-2019-14575)
>
> .../DxeImageVerificationLib.c | 291 ++++++++++++------
> 1 file changed, 198 insertions(+), 93 deletions(-)
>
Please put a space character in all the subject lines before the
"(CVE-2019-14575)" part.
Thanks
Laszlo
next prev parent reply other threads:[~2020-02-17 7:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 7:27 [PATCH v2 00/10] Fix false negative issue in DxeImageVerificationHandler Wang, Jian J
2020-02-14 7:27 ` [PATCH v2 01/10] SecurityPkg/DxeImageVerificationLib: Fix memory leaks(CVE-2019-14575) Wang, Jian J
2020-02-14 7:27 ` [PATCH v2 02/10] SecurityPkg/DxeImageVerificationLib: reject CertStack.CertNumber==0 per DBX(CVE-2019-14575) Wang, Jian J
2020-02-14 7:27 ` [PATCH v2 03/10] SecurityPkg/DxeImageVerificationLib: fix wrong fetch dbx in IsAllowedByDb(CVE-2019-14575) Wang, Jian J
2020-02-14 7:27 ` [PATCH v2 04/10] SecurityPkg/DxeImageVerificationLib: avoid bypass in fetching dbx(CVE-2019-14575) Wang, Jian J
2020-02-14 7:27 ` [PATCH v2 05/10] SecurityPkg/DxeImageVerificationLib: refactor db/dbx fetching code(CVE-2019-14575) Wang, Jian J
2020-02-14 7:27 ` [PATCH v2 06/10] SecurityPkg/DxeImageVerificationLib: Differentiate error/search result (1)(CVE-2019-14575) Wang, Jian J
2020-02-14 7:47 ` Yao, Jiewen
2020-02-14 7:27 ` [PATCH v2 07/10] SecurityPkg/DxeImageVerificationLib: tighten default result(CVE-2019-14575) Wang, Jian J
2020-02-14 7:27 ` [PATCH v2 08/10] SecurityPkg/DxeImageVerificationLib: plug Data leak in IsForbiddenByDbx()(CVE-2019-14575) Wang, Jian J
2020-02-14 7:27 ` [PATCH v2 09/10] SecurityPkg/DxeImageVerificationLib: Differentiate error/search result (2)(CVE-2019-14575) Wang, Jian J
2020-02-14 7:27 ` [PATCH v2 10/10] SecurityPkg/DxeImageVerificationLib: change IsCertHashFoundInDatabase name(CVE-2019-14575) Wang, Jian J
2020-02-14 7:46 ` Yao, Jiewen
2020-02-17 7:48 ` Laszlo Ersek [this message]
2020-02-17 7:51 ` [edk2-devel] [PATCH v2 00/10] Fix false negative issue in DxeImageVerificationHandler Wang, Jian J
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-list 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=9c8b47c7-765a-6064-49c3-a0a9578ccba6@redhat.com \
--to=devel@edk2.groups.io \
/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