SSD vulnerabilities with hardware encryption allow attackers to easily circumvent defensive measures

3r380.  
3r380.  
Researchers at the University of Radboud (Netherlands) 3r34343. told r3r377. about vulnerabilities in the protection system of some solid-state drives. They allow an attacker to bypass the disk encryption function and access information on the disk without having to know the access password. 3r380.  
3r380.  
True, the voiced problem concerns only those SSD models that support hardware encryption due to the presence of an embedded chip that is separate from the main module. 3r380.  
The problem is 3r377. that there is a way to access data without a password at all - you need to use a vulnerability in the SED firmware. Vulnerabilities of this kind affect the specifications "3r3-3327. ATA security " And " TCG Opal ". 3r380.  
3r380.  
The main problem is that in addition to the access passwords that are specified by the owners of the SSD, there is also a master password, which is set in the factory. If you change this password, the vulnerability in question is eliminated, if not, the SSD and its data are open to attackers - of course, those who know exactly what to do. 3r380.  
3r380.  
But there is also a snag: the fact is that as a result of the flaws of the manufacturers of such devices, the encryption password chosen by the user and the DEK encryption key are not cryptographically linked. In other words, an attacker can find out the DEK value (the necessary data is hidden inside the SED chip) and then use it to decrypt the data without having to know the user-defined password. 3r380.  
3r380.  
“The lack of a cryptographic bundle is a catastrophe. Due to a flaw, user data is weakly protected. The data stored on the disk can be easily restored and copied, ”says one of the researchers who discovered the problem. The results of the research and the experts published their conclusions in the form of an article (download Here ). 3r380.  
3r380.  
Unfortunately, scientists were able to examine a small number of solid-state drives, their models are indicated below. However, all the studied devices were vulnerable. 3r380.  
3r380.  
3r380.  
3r380.  
The researchers studied both external and embedded SSD with hardware encryption support. In their opinion, a much more extensive range of such devices is subject to hacking. The study was completed in April of this year, until now scientists, together with the police of the Netherlands, tried to inform all manufacturers of the devices studied about the problem. 3r380.  
3r380.  
It is reported that companies such as Crucial (Micron) and Samsung have released a firmware update for solid-state drives, thus solving the problem. True, this may not be enough. 3r380.  
3r380.  
The fact is that researchers began to deepen their work, conducting a study of the security of user data of different systems. Windows users are most at risk because in this OS some services exacerbate the problem. So, the problem can be called Windows BitLocker, a software-based system for encrypting data on a disk running in the Windows OS environment. 3r380.  
3r380.  
As soon as BitLocker detects SSD with hardware encryption, the service is disabled, and the data is not encrypted by Windows, the OS "hopes" for hardware support. So, users who are still working with SSD Сracial and Samsung and have not updated the firmware of their drives, in fact, keep their data open to all. 3r380.  
3r380.  
The good news is that BitLocker can still be made to work in this case; to do this, you need to change some of the settings for
Group Policy 3r377. . But in this case, you need to format the drive and start working with it from scratch. 3r380.  
3r380.  
But in this case, the protection is double and there are no particular problems. According to the researchers who discovered the problem, its root is in the specifications created by the developers of hardware encryption. 3r388.
! function (e) {function t (t, n) {if (! (n in e)) {for (var r, a = e.document, i = a.scripts, o = i.length; o-- ;) if (-1! == i[o].src.indexOf (t)) {r = i[o]; break} if (! r) {r = a.createElement ("script"), r.type = "text /jаvascript", r.async =! ? r.defer =! ? r.src = t, r.charset = "UTF-8"; var d = function () {var e = a.getElementsByTagName ("script")[0]; e. ): d ()}}} t ("//mediator.mail.ru/script/2820404/"""_mediator") () (); 3r3386.
3r388.