On May 1st 2017, Intel published a security advisory regarding a firmware vulnerability in certain systems that utilize Intel® Active Management Technology (AMT), Intel® Standard Manageability (ISM) or Intel® Small Business Technology (SBT). The vulnerability could enable a network attacker to remotely gain access to business PCs or devices that use these technologies.
There is an escalation of privilege vulnerability in Intel® Active Management Technology (AMT), Intel® Standard Manageability (ISM), and Intel® Small Business Technology versions firmware versions 6.x, 7.x, 8.x 9.x, 10.x, 11.0, 11.5, and 11.6 that can allow an unprivileged attacker to gain control of the manageability features provided by these products. This vulnerability does not exist on Intel-based consumer PCs with consumer firmware, Intel servers utilizing Intel® Server Platform Services (Intel® SPS), or Intel® Xeon® Processor E3 and Intel® Xeon® Processor E5 workstations utilizing Intel® SPS firmware.
There are two ways this vulnerability may be accessed, please note that Intel® Small Business Technology is only vulnerable to the second method:
Severe.
Our customer's security is paramount, to that end Stone are working with key vendors to provide firmware updates which close this vulnerability as quickly as possible. Those updates will be able available to download from this article as soon as they are made available to us
Intel has released a discovery tool which will analyse your systems for the vulnerability.
Actions:
1. Determine if you have an Intel® AMT, Intel® SBA, or Intel® ISM capable systems. If you determine that you do not have an Intel® AMT, Intel® SBA, or Intel® ISM capable system then no further action is required.
2. Utilize the INTEL-SA-00075 Detection Guide to assess if your system has the impacted firmware.
3. Stone highly recommends updating affected systems Management Engine (ME) firmware as soon as they become available. Please review the affected products section of this article for ME firmware update availability.
4. If a firmware update is not yet available, mitigations are provided by the INTEL-SA-00075 Mitigation Guide. It is recommended that unpatched systems should have the steps detailed in the mitgation guide applied to them until such time as an ME firmware update becomes available.
The issue has been observed in Intel manageability firmware versions 6.x, 7.x, 8.x 9.x, 10.x, 11.0, 11.5, and 11.6 for Intel® Active Management Technology, Intel® Small Business Technology, and Intel® Standard Manageability. Versions before 6 or after 11.6 are not impacted.
Where possible, updated BIOSes or patches for Management Engine Firmware are shown below. This article will be updated as more BIOSes or patches become available.
StonePC Lite/Tower / All In One
Product code / General BIOS Update Link |
Motherboard model |
Updated ME Download |
BOAMOT-458 | Asus P8B75-M |
(Asus Ivybridge) Windows Patch: 8.1.x.3608 |
BOAMOT-461 | Asus P8Q77-M | |
Asus B85M-E |
(Asus Haswell) Windows Patch: 9.1.41.3024 (updated 29/6/17 with improved update utility) DOS Patch: 9.1.41.3024 |
|
Asus CS-B |
||
Asus Q87T |
||
Asus Q87M-E |
||
Asus B150M-A |
(Asus Skylake / Kaby Lake) Windows Patch: 11.6.27.3264 DOS Patch: 11.6.27.3264 |
|
Asus Q170M-C |
||
Asus Q170T |
||
Asus B150M-A/M.2 |
||
Asus B250M-A | ||
Asus Q270M-C |
||
ISRMOT-174 | Gigabyte MW50-SV0 |
(Gigabyte C612 Xeon Workstation) BIOS R06 with patched Workstation / HEDT ME Firmware. |
Legacy Desktop Products
Stock code |
Motherboard model |
Patched ME firmware |
DQ57TM |
Windows Patch: 6.2.61.3635 |
|
DQ67SW |
Windows Patch: 7.1.91.3272 | |
DQ67OW |
||
DQ67EP |
||
DQ77MK |
Windows Patch: 8.1.71.3708 |
|
DB75EN |
||
DQ77CP |
||
DQ77KB |
Further information regarding Intel’s release schedule for their own branded desktop products can be found here.
StonePC Micro
Stock code |
Kit model |
Motherboard model |
Patched ME firmware |
INTNUC-10007 |
DC53427HYE |
D53427RKE |
Windows BIOS: 8.1.71.3608 |
INTNUC-10009 |
NUC5i5MYHE |
NUC5i5MYBE |
Windows BIOS: 10.0.55.3000 |
Stone Notebooks
Chassis Part Code |
Notebook Model |
Patched ME firmware |
NT310 |
Not currently available, please follow mitigating actions. |
|
NT310 |
Applies to:
Asus B150M-A/M.2 |
Intel Management Engine (Intel ME 11.0.0-11.7.0), Intel Trusted Execution Engine (Intel TXE 3.0), and Intel Server Platform Services (Intel SPS 4.0) vulnerability (Intel-SA-00086)
Summary
On November 20th 2017, Intel published a security advisory regarding a firmware vulnerability in certain systems that utilize ME Firmware versions 11.0 / 11.5 / 11.6 / 11.7 / 11.10 / 11.20, SPS Firmware version 4.0, and TXE version 3.0.
Please download and view the document attached to this article for further information and firmware / BIOS patch availability.
Note: The attached document will be updated as new information becomes available.
Applies to:
BitLocker is a security technology incorporated into Microsoft Windows operating systems starting from Windows 8, which is intended to protect users by encrypting data stored on a device, or external storage media (such as USB hard disk drives).
During the ongoing development of Windows 10, Microsoft made a change which sought to automatically provide this data security to its customers by activating BitLocker for devices which were designed to meet modern hardware standards.
With the continued evolution of hardware standards, alongside the release of Windows 11 24H2 Microsoft have now introduced a reduced set of hardware requirements which devices need to meet to become eligible for BitLocker automatic encryption.
Going forward from Windows 11 24H2 the requirements will be:
This essentially means all Stone brand devices which already meet the hardware requirements for Windows 11 (external link), are now in-scope for BitLocker automatic encryption.
Following a clean installation of Windows 11 24H2 (Home, Professional, Enterprise and Education) and the completion of OOBE (Out Of Box Experience) where users go through the initial Windows setup, BitLocker will initialise and prepare to encrypt data on all fixed internal storage drives.
However, data encryption will not take effect until the first time a user logs into the device using a Microsoft Account (available for individual users) or an Azure Active Directory Account (likely to be provided by an education institution or employer).
Once either of these two scenarios occur, BitLocker will arm, link the encryption keys to your account and store them in the cloud.
We strongly recommend that all users or administrators ensure that BitLocker keys are backed up, as they will be required if a device enters BitLocker Recovery Mode for any reason.
BitLocker recovery mode can occur for many reasons including hardware or software changes, below are some examples:
Authentication errors:
Boot/BIOS changes:
Hardware, software and firmware changes:
Other triggers:
If BitLocker recovery mode occurs, you'll be prompted to input a BitLocker recovery key, which is a 48-digit number.
Prompting for the recovery key will either occur during start-up, due to a security risk or hardware change:
Or you may be prompted to input the recovery key for data and/or external drives, for example if you forgot the unlock password:
When you are prompted to enter a BitLocker recovery key, take note of the first 8 digits of the recovery key ID.
The recovery key ID helps identifying which recovery key to use, in case you have more than one.
Where BitLocker automatic encryption has occurred, there are primarily two places where your recovery key might be.
Attached to your Microsoft Account
If the BitLocker recovery key is backed up to your Microsoft Account, follow these steps to retrieve it.
From another device, open a web browser and go to https://aka.ms/myrecoverykey
Sign in with your Microsoft account and locate the key ID:
Use the related recovery key to unlock the drive.
If your device was ever signed into an organization using a work or school account, the recovery key could be stored in that organization's account. You might be able to access it directly, or you might need to contact the IT support for that organization to access your recovery key.
From another device, open a web browser and go to https://aka.ms/aadrecoverykey
Sign in with your work or school account
Select Devices and expand the device for which you need to retrieve the recovery key
Select the option View BitLocker Keys
Using the key ID, find the related recovery key and use it to unlock the drive.
If your device is managed by an organisation, check with their IT department to retrieve the recovery key.
If you can’t find the BitLocker recovery key and are unable to undo any changes that caused it to be needed, you’ll have to reset your device.
Resetting your device will remove all of your files.
Affected products: