-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hughsie/zhangyoufu #5
base: master
Are you sure you want to change the base?
Conversation
@zhangyoufu your review please. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You must obtained this file from WinSxS directory. I found two samples that match your date & time.
You can find win32 FILETIME in _manifest_.cix.xml
file, and a little-endian uint64 after the PA30
magic string in the delta file.
This one contains x86_microsoft-windows-s..boot-firmwareupdate_31bf3856ad364e35_6.2.9200.16895_none_b16766b7d6f0546c
with 130419008663852453
(2014-04-13 22:14:26).
This one contains amd64_microsoft-windows-s..boot-firmwareupdate_31bf3856ad364e35_6.2.9200.16895_none_0d86023b8f4dc5a2
with 130419008688273408
(2014-04-13 22:14:28).
I would prefer to use KB / UEFI Forum release date, instead of mtime of dbxupdate.bin file which may be days or months before the release date. Every single KB comes with many msu/cab with different mtime. It's messy.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, that works for me. Would you mind submitting a pull request to this branch to fix this up please?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This update removed 61341e07697978220ea61e85dcd2421343f2c1bf35cc5b8d0ad2f0226f391479
, an x64 entry introduced in DBXUpdate-20200729.x64.bin
, which may worth mention.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
AFAIK, CVE-2023-28005 is not related to this release.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CVE-2023-28005 describes a vulnerability in Trend Micro Endpoint Encryption Full Disk Encryption version 6.0.0.3204 and below. We shouldn't mention it in a DBXUpdate that deals with VMware esx-boot. mboot-official_arm64.efi
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agree. Can you include that in your pull request please. I'd be very grateful for any help.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CVE-2023-28005 describes a vulnerability in Trend Micro Endpoint Encryption Full Disk Encryption version 6.0.0.3204 and below. We shouldn't mention it in a DBXUpdate that deals with VMware esx-boot. mboot-official_em64t.efi
Many thanks to Youfu Zhang! Fixes #4
b6c6f98
to
16a4799
Compare
No description provided.