

So it is down to the Vendors to patch there software or be left with complaints.Ĭorsair have also acknowledged they are looking in to this issue.Anticheats uses heartbeats so you can't simply disable the anticheat and stop it from running since it keeps communicating with their servers.

I don't think Riot Games will add anything to a whitelist because Vanguard is apart of an online data base that has know exploits and vulnerability's that allow cheats though the code. Official CPU-z is currently on Versions 1.92 last updated this week. The version of CPU-z that ICUE is currently using is Version 1.49 (cpuz149) the code is from 2008 that has exploits and vulnerability's leaving a hole in the system. I don't believe that's the case because Icue uses cpuz149_圆4.sys to monitor system temps and voltages and that cpuz149 driver is vulnerable and exploitable hence why vanguard blocked it will vanguard whitelist cpuz149 i would doubt it. The anti-cheat thinks it may be a cheat related file unfortunately, Vanguard will have to whitelist the file." This will happen to all other software using CPUz data, not just ours. I reached out via twitter an this is what corsair support said Seems like the correct way foward is to just not rely on this specific driver. Note that the CPU-Z driver provides numerous other IOCTLs that could be used for exploitation, such as reading from and writing to arbitrary model-specific registers. Without the ability to read the page table base from cr3, the exploitation method in this project is no longer feasible. Furthermore, the IOCTL to read control registers has been removed (although the physical memory read/write implementations remain). Note that when running as an Administrator, it is trivial to enable this privilege from usermode. If this privilige is missing or disabled, the driver will reject the request with STATUS_ACCESS_DENIED. On requests to open the driver's device object, it will check to see if the current process has the SeLoadDriverPrivilege enabled.


From :Īs of version 1.81, the driver provided with CPU-Z has been patched to limit the set of callers that can open its device object and some IOCTL implementations have been removed. Edit: Latest version of CPU-Z also has an outdated driver.
