Reply to thread

Message

<blockquote data-quote="ExecutiveOrder" data-source="post: 961674" data-attributes="member: 93099">Yes, it (and other security products) still can block HTTPS because they don&#039;t necessarily encrypt the domain of the web (or maybe other stuff as an indicator, like port or IP, or connection to other servers/C2 perhaps?), but if the issue is the transmitted data (content like <a href="https://malwaretips.com/threads.html" target="_blank">https://malwaretips.com/threads.html</a> for example) is encrypted, it needed to leave the network cryptographic protocol (like TLS) during the communication process between server and client so the data is readable, made it to disk or browser temporary memory before written into the disk (and most of the cases, it can be blocked easily even without intercepting the data transmitted inside encrypted connection).I&#039;ve read a lot of Palant&#039;s bug hunting discoveries some time ago and it basically discusses vulnerabilities that could be discovered on an everyday basis of software no matter what vendor and what component it is. In the particular reports, this was a problem from 2018, you can check <a href="https://hackerone.com/kaspersky/hacktivity?type=team" target="_blank">Hackerone bug bounty program</a> from Kaspersky in this report (links below), this was already addressed and fixed in 2019. Palant is one of the helpful bounty hunters or ethical hackers who report vulnerabilities to Kaspersky the most there and have been rewarded at least $9300, most of the reports were approved (8 out of 10) except those two in his blog.And most likely, the particular components mentioned here have already undergone a lot of changes and have been improved since then (it&#039;s been 2 years since the reports were closed/solved).</blockquote>

[QUOTE="ExecutiveOrder, post: 961674, member: 93099"] Yes, it (and other security products) still can block HTTPS because they don't necessarily encrypt the domain of the web (or maybe other stuff as an indicator, like port or IP, or connection to other servers/C2 perhaps?), but if the issue is the transmitted data (content like [URL]https://malwaretips.com/threads.html[/URL] for example) is encrypted, it needed to leave the network cryptographic protocol (like TLS) during the communication process between server and client so the data is readable, made it to disk or browser temporary memory before written into the disk (and most of the cases, it can be blocked easily even without intercepting the data transmitted inside encrypted connection). I've read a lot of Palant's bug hunting discoveries some time ago and it basically discusses vulnerabilities that could be discovered on an everyday basis of software no matter what vendor and what component it is. In the particular reports, this was a problem from 2018, you can check [URL='https://hackerone.com/kaspersky/hacktivity?type=team']Hackerone bug bounty program[/URL] from Kaspersky in this report (links below), this was already addressed and fixed in 2019. Palant is one of the helpful bounty hunters or ethical hackers who report vulnerabilities to Kaspersky the most there and have been rewarded at least $9300, most of the reports were approved (8 out of 10) except those two in his blog. And most likely, the particular components mentioned here have already undergone a lot of changes and have been improved since then (it's been 2 years since the reports were closed/solved). [/QUOTE]

Verification