Intel Rapid Storage Technology Vulnerability Allows Persistent Malware

(Image credit: Shutterstock)
3

Researchers from Safe Breach discovered that an older version of Intel’s Rapid Storage Technology (RST) software is vulnerable to DLL hijacking. The flaw could allow a malicious program to be seen as trusted by antivirus engines, thus bypassing their system protection. 

In order to exploit the vulnerability, the attacker needs administrative privileges. However, this may be an easier task than many might think, as the vast majority of Windows systems run with administrative privileges enabled by default, making an attacker’s job that much easier. 

Latest Videos FromTom's Hardware
Contributor

Lucian Armasu is a Contributing Writer for Tom's Hardware US. He covers software news and the issues surrounding privacy and security.

  • Pat Flynn
    It would be nice to know the names of the DLL files the EXE is looking for. With that info, you should be able to create empty dummy files, then use CACLS to block access to said DLL files preventing it from being overwritten by any trojan. Sort of a preventative method?
    Reply
  • JonDol
    Pat Flynn said:
    It would be nice to know the names of the DLL files the EXE is looking for. With that info, you should be able to create empty dummy files, then use CACLS to block access to said DLL files preventing it from being overwritten by any trojan. Sort of a preventative method?

    That could be indeed useful for some advanced users. I personally use Comodo Security Suite which is quite helpful to prevent DLL hijacking. Using the 'Purge' functionality is removes the trust of no longer existing binary files thus when they pop up again you are required to allow them. You are also required to take action when a trusted binary gets updated. At least, this is how I configured mine thus no need to fiddle with CACLS.
    Reply
  • TreborG2
    Pat Flynn said:
    It would be nice to know the names of the DLL files the EXE is looking for. With that info, you should be able to create empty dummy files, then use CACLS to block access to said DLL files preventing it from being overwritten by any trojan. Sort of a preventative method?
    I believe they blocked them to lessen the pubic ability to openly use said file names .. as well as to limit the script kiddies etc..
    Reply