There was a pervasive sense of contentedness everywhere you turned with the current model where what was inside a handset was largely a black box. Manufacturers weren't yet open to disclosing what silicon was inside, and there wasn't any SoC messaging or branding from any of the numerous silicon vendors. I'd expect Riot to fix this as soon as possible.About three years ago, I remember one of the biggest problems I had while sorting out phones was figuring out what SoCs were inside them. 145 and above should be unproblematic, and it seems like an oversight that Vanguard is still blocking it. In conclusion: If Vanguards reports that it's blocking a cpuz sys file with a versioning lower than 144, it's in the right, and you're running unsafe software. This seems like an unintentionally wide ban on behalf of Vanguard.Īlso, I will quote the linked comment for posterity:įYI the version of CPU-Z doesn't match the version string of the driver:ĬPU-Z v1.81: cpuz_144圆4.sys (last known vulnerable) I know CAM to ue cpuz_149圆4.sys, however, which is still blocked. Based on this comment, the vulnerability is non-existent in cpuz_145圆4.sys and above. The vulnerability has, however, been patched since 2017.
NOTE: the vendor indicates that the arbitrary read itself is intentional behavior (for ACPI scan functionality) the security issue is the lack of an ACL.Īnd based on this, it's understandable that Vanguard nopes hard on it. Furthermore, the driver can map any physical page on the system and returns the allocated map page address to the user: that results in an information leak and EoP.
Any application running on the system (Windows), including sandboxed users, can issue an ioctl to this driver without any validation. In CPUID CPU-Z through 1.81, there are improper access rights to a kernel-mode driver (e.g., cpuz143_圆4.sys for version 1.43) that can result in information disclosure or elevation of privileges, because of an arbitrary read of any physical address via ioctl 0x9C402604. The CPU-Z driver had a vulnerability up to, and including, version 1.81, which was abused by hackers - both the cheating and the bank-account-stealing kinds.ĬVEDetails report followign on the vulnerability: MSI Afterburner, NZXT CAM and programs like them are often using it. They are the makers of CPU-Z, the drivers of which are utilized in many other proprietary programs. If you don't know CPUID, you've probably still used their software, in one form or another.
0 kommentar(er)
