Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Software
Security Apps
Other security for Windows, Mac, Linux
HitmanPro 3.8.18 build 312
Message
<blockquote data-quote="Zero Knowledge" data-source="post: 868976" data-attributes="member: 57429"><p>Local privesc in security software is bad, really bad and I can't believe they would not know about a local privesc through testing production ready releases of HMP in the lab. This bug would own most users of HMP.Alert if they ran a scan with the anti-malware engine incorporated into HMP.Alert which is HMP.</p><p></p><p>Find out when this bug was introduced and how many builds had this exploit before the fix and who was targeted (because they would know if the bug was fixed and by licensing servers of those who were targeted) the picture will get clearer. Exploits like this is a perfect way to own users while claiming deniability by a company. They didn't break the security program or encryption there was a bug/exploit in the code. If it smells like crap, looks like crap, it is crap.</p><p></p><p>If this exploit was a genuine mistake by development I would think they would be more forthcoming and honest.</p></blockquote><p></p>
[QUOTE="Zero Knowledge, post: 868976, member: 57429"] Local privesc in security software is bad, really bad and I can't believe they would not know about a local privesc through testing production ready releases of HMP in the lab. This bug would own most users of HMP.Alert if they ran a scan with the anti-malware engine incorporated into HMP.Alert which is HMP. Find out when this bug was introduced and how many builds had this exploit before the fix and who was targeted (because they would know if the bug was fixed and by licensing servers of those who were targeted) the picture will get clearer. Exploits like this is a perfect way to own users while claiming deniability by a company. They didn't break the security program or encryption there was a bug/exploit in the code. If it smells like crap, looks like crap, it is crap. If this exploit was a genuine mistake by development I would think they would be more forthcoming and honest. [/QUOTE]
Insert quotes…
Verification
Post reply
Top