-
Notifications
You must be signed in to change notification settings - Fork 16
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
Support Intel SA-00086 detection for ME firmware #37
Comments
@texhex https://communities.intel.com/message/521691#521691 Regards |
@GregoryMachin Dang it. This would mean that running the SA-86 tool on a system that is affected by SA-75 but not SA-86 would result in the tool reporting "All good". I think I will use the 4.0 rewrite to strip down the ME part that we ONLY use the ME version to detect if an update is necessary or not, as we already do with BIOS and TPM updates (No special "Is Vulnerable" detection). Thanks for pointing this out! P.S.: Awesome username you use on the Intel site : ) |
Thanks, yeah been using the username since early 2000s and have seen anyone
else using it lol.
It's annoying it would have been good if they where accumulative. Would
need to run them both for true results.
I agree used the same methode as the bios and tpm.
G
On 24/01/2018 19:56, "Michael Hex" <[email protected]> wrote:
@GregoryMachin <https://github.com/gregorymachin> Dang it. This would mean
that running the SA-86 tool on a system that is affected by SA-75 but not
SA-86 would result in the tool reporting "All good".
I think I will use the 4.0 rewrite to strip down the ME part that we ONLY
use the ME version to detect if an update is necessary or not, as we
already do with BIOS and TPM updates (No special "Is Vulnerable" detection).
Thanks for pointing this out!
P.S.: Awesome username you use on the Intel site : )
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#37 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Ab67YuKht2qYSVtpabNdJ6oA0uJtUlo0ks5tNtQbgaJpZM4RkZEk>
.
|
@GregoryMachin 4.0 BETA code is now online (no release so far, as the documentation is missing) but the changes are included. I will check if I also include the changes proposed #36 so a on-the-fly BIOS change for ME will also be added. Closing this issue now, please reopen if you think this requires more attention. |
In 2017-11 another ME security bug was found: Intel SA 00086 / HPSBHF03571 (aka CVE-2017-5705, CVE-2017-5706, CVE-2017-5707, CVE-2017-5708, CVE-2017-5709, CVE-2017-5710, CVE-2017-5711)
Given that this bug is newer then the one noted in HPSBHF03557/ Intel SA 00075, we believe a system that is secured against SA 00086 is also secured against SA 00075.
We should therefore replace the SA-75 detection tool with the SA-86 detection tool and update the ME firmwares with new firmware files.
The text was updated successfully, but these errors were encountered: