From: "Doug Flick via groups.io" <dougflick=microsoft.com@groups.io>
To: devel@edk2.groups.io
Cc: Saloni Kasbekar <saloni.kasbekar@intel.com>,
Zachary Clark-williams <zachary.clark-williams@intel.com>
Subject: [edk2-devel] [PATCH v1 0/3] Corrects additional concern in NetworkPkg
Date: Thu, 8 Feb 2024 16:20:34 -0800 [thread overview]
Message-ID: <20240209002037.10414-1-doug.edk2@gmail.com> (raw)
This patch series corrects an additional security concern
found in Dhc6Dxe related to CVE-2023-45229.
Additionally this fixes some issues on the mailing list
that were not pulled in before merging into Edk2.
Cc: Saloni Kasbekar <saloni.kasbekar@intel.com>
Cc: Zachary Clark-williams <zachary.clark-williams@intel.com>
Doug Flick (3):
NetworkPkg: Dhcp6Dxe: SECURITY PATCH CVE-2023-45229 Related Patch
NetworkPkg: Dhcp6Dxe: Additional Code Cleanup
NetworkPkg: : Updating SecurityFixes.yaml
NetworkPkg/Dhcp6Dxe/Dhcp6Io.c | 232 +++++++++++---------
NetworkPkg/Dhcp6Dxe/Dhcp6Utility.c | 20 +-
NetworkPkg/SecurityFixes.yaml | 1 +
3 files changed, 141 insertions(+), 112 deletions(-)
--
2.43.0
next reply other threads:[~2024-02-08 23:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-09 0:20 Doug Flick via groups.io [this message]
2024-02-08 23:45 ` [edk2-devel] [PATCH v1 0/3] Corrects additional concern in NetworkPkg Doug Flick via groups.io
2024-02-09 0:20 ` [edk2-devel] [PATCH v1 1/3] NetworkPkg: Dhcp6Dxe: SECURITY PATCH CVE-2023-45229 Related Patch Doug Flick via groups.io
2024-02-09 0:20 ` [edk2-devel] [PATCH v1 2/3] NetworkPkg: Dhcp6Dxe: Additional Code Cleanup Doug Flick via groups.io
2024-02-09 0:20 ` [edk2-devel] [PATCH v1 3/3] NetworkPkg: : Updating SecurityFixes.yaml Doug Flick via groups.io
-- strict thread matches above, loose matches on Subject: below --
2024-02-09 0:23 [edk2-devel] [PATCH v1 0/3] Corrects additional concern in NetworkPkg Doug Flick via groups.io
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=20240209002037.10414-1-doug.edk2@gmail.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