#What is avast safe zone code
It is their duty to identify any issues in the SafeZone code before the bad guys are able to exploit it. Chromium is a rapidly updated project and vendors such as Avast need to keep pace with the fast release cycle.
There is no excuse for missing this issue. Should the firm have spotted the issue earlier? Nevertheless, this doesn’t take away from the fact that it is an avoidable issue and, as such, entirely unacceptable. A number of other companies, including Comodo and Malwarebytes, are also on the Google hit list for poor implementation on top of Chromium that has generated security flaws. Sadly, Avast is not alone in its failings. This type of issue should have been easily flagged in product testing. Quite frankly, an IT security company like Avast should not have fallen victim to a hole in the Chromium security chain. This type of vulnerability is due to rapid release cycles and inadequate security testing.
How could such a flaw have happened in a “secure” browser from an IT security company? Chris Underhill Head of IT and Security at UK-based cyber security firm, Cyber Security Partners have the following comments on the Avast SafeZone flaw.Ĭhris Underhill, Head of IT and Security at UK-based Cyber Security Firm, Cyber Security Partners:
0 kommentar(er)
