DirtyMoe: Code Signing Certificate

Avast - 

Abstract

The uses a driver signed with a revoked that can be seamlessly loaded into the Windows kernel. Therefore, one of the goals is to analyze how Windows works with a code signature of Windows drivers. Similarly, we will be also interested in the code signature verification of user-mode applications since the user account control (UAC) does not block the application execution even if this one is also signed with a revoked certificate. The second goal is a statistical of certificates that sign the DirtyMoe driver because the certificates are also used to sign other malicious . We focus on the determination of the certificate’s origin, prevalence, and a quick analysis of the top 10 software signed with these certificates.

Contrary to what often has been assumed, Windows loads a driver signed with a revoked certificate. Moreover, the results indicate that the UAC does not verify revocation online but only via the system local storage which is updated by a user manually. DirtyMoe certificates are used to sign many other software, and the number of incidents is still growing. Furthermore, Taiwan and seem to be the most affected by these faux signatures.

Overall, the analyzed

Read More: https://decoded.avast.io/martinchlumecky/dirtymoe-3/?utm_source=rss&utm_medium=rss&utm_campaign=dirtymoe-3