But here\u2019s the thing. The Chrome and Firefox versions for desktop computers and Android are built on Google\u2019s V8 engine and Mozilla\u2019s Gecko\/Quantum engine, respectively. However, it\u2019s a different story for iPhones. In keeping with Apple\u2019s policies, there is only one<\/a> engine permitted in iOS \u2014 you guessed it: WebKit. This means that all browsers for iOS are essentially Safari with different user interfaces.<\/p>\n Excerpt from the iOS app developer rules: \u201cApps that browse the web must use the appropriate WebKit framework and WebKit JavaScript.\u201d<\/p><\/div>\n This means that all vulnerabilities found in WebKit present a danger for users of any<\/em> browsers for iOS. Since iPhones are a very tempting target for hackers, security specialists study the WebKit engine all the more closely, and as a result, they find vulnerabilities in it rather often. This includes vulnerabilities that attackers are already using in the wild.<\/p>\n One of the most dangerous types of vulnerabilities in a browser engine is a so-called zero-click vulnerability, which allows bad actors to infect an iPhone without any action by the user. When this kind of vulnerability is exploited, the user doesn\u2019t need to be convinced to download or install anything. All the attacker needs do is draw the victim to a specially built website with malicious code or hack a popular site and implant the malicious code in it. After the user visits such a site through a vulnerable browser, the attackers can take control of the iPhone.<\/p>\n It\u2019s important to remember that the update of the WebKit engine and Safari browser isn\u2019t related to the update of the browser apps you\u2019re using. Google Chrome automatically updates from the App Store \u2014 that is, if you haven\u2019t disabled this option, and we don\u2019t recommend that you do \u2014 but in essence this is an update of the shell program, not the engine. So this won\u2019t solve the problem of vulnerabilities in WebKit.<\/p>\n To avoid vulnerabilities in both the WebKit engine and Safari browser, you need to install the appropriate iOS updates. The best thing to do is to make sure to install all the latest operating system updates \u2014 after all, the vulnerabilities aren\u2019t just in the browser engine but also in other important components of iOS.<\/p>\n To update your iPhone, go to Settings \u2192 General \u2192 Software Update<\/em>. If you see a button on the screen that says Download and Install<\/em>, tap it and follow the instructions.<\/p>\n Where to find the iOS update in your iPhone\u2019s settings<\/p><\/div>\n A lot of users are lukewarm about updating the operating system: some people don\u2019t like having to get used to new features in the interface, some worry about having less storage, while others fear that after an update the iPhone may start to slow down or some old apps that are no longer supported in the new version will stop working.<\/p>\n These fears aren\u2019t totally unfounded. It\u2019s true that Apple does sometimes make the interface less user-friendly. It\u2019s also true that each new version of the system takes up a bit more storage than the previous one and leaves less space for your files. And it\u2019s no myth that iPhones have slowed down after an update \u2014 this has been documented<\/a>.<\/p>\n![\"Excerpt](\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/92\/2022\/04\/04092940\/always-update-safari-on-iphone-webkit.jpg\")
<\/a>How to update Safari and WebKit<\/h2>\n
![\"Where](\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/92\/2022\/04\/04092847\/always-update-safari-on-iphone-settings-EN.png\")
<\/a>Don\u2019t be afraid of iOS updates<\/h2>\n