People can actively write exploits, let alone copying some vulnerable binary to trigger some known exploit. If you assume the local user is malicious, then you are totally right.
This is largely true for all local privilege escalation vulnerabilities.
This means that the vulnerability isn't really with 7zip at all, but with Microsoft, and there is no type of mitigation until Microsoft patches it.Depends on the threat model, whether you consider your end user trusted or not. So that means there really is no mitigation to this other than, maybe, application blacklisting?Įxpanding on the above, that means it would be far easier for someone to create a malicious dll file that explots the inherent vulnerability in Microsoft's CHM system, and then you have an exploit that doesn't depend on 7zip at all. Stealth006 said:The mitigation steps don't quite make sense to me, because if someone really wanted to exploit this, they would just have to download the affected 7zip executable, the affected chm file, and the specifically crafted 7z file to any system, and voila.
0 kommentar(er)
