{"id":101262,"date":"2021-09-13T22:22:38","date_gmt":"2021-09-13T20:22:38","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/novaya-tehnika-ekspluataczii-uyazvimostej-klassa-spectre-v-chrome"},"modified":"2021-09-13T22:22:38","modified_gmt":"2021-09-13T20:22:38","slug":"novaya-tehnika-ekspluataczii-uyazvimostej-klassa-spectre-v-chrome","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/novaya-tehnika-ekspluataczii-uyazvimostej-klassa-spectre-v-chrome","title":{"rendered":"New exploitation techniques for Spectre vulnerabilities in Chrome.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
A group of researchers from American, Australian, and Israeli universities has proposed a new side-channel attack technique to exploit Spectre-class vulnerabilities in browsers based on the Chromium engine. The attack, codenamed Spook.js, allows an attacker to bypass site isolation mechanisms through the execution of JavaScript code, enabling access to the entire address space of the current process. This means that data from pages opened in other tabs, but processed in the same process, can be read. <\/p>\n
Since Chrome runs different sites in different processes, the potential for practical attacks is limited to services that allow different users to host their pages. This method enables an attacker to determine the presence of other pages that the user has open from the same site, from a page where they can embed their JavaScript code, and extract confidential information such as credentials or banking details auto-filled by the form-filling system. As a demonstration, it shows how one could attack someone else's blog on Tumblr if its owner opens an attacker\u2019s blog in another tab hosted on the same service.
\r\n \r\n
<\/div>\r\n <\/div><\/center> <\/p>\n
Another application of this method involves attacks on browser extensions, allowing an attacker-controlled extension to extract data from other extensions upon installation. As an example, it demonstrates how, by installing a malicious extension, one can retrieve sensitive information from the LastPass password manager.
\r\n \r\n
<\/div>\r\n <\/div> <\/center> <\/p>\n
Researchers have released a prototype exploit that works in Chrome 89 on systems with Intel i7-6700K and i7-7600U CPUs. The exploit was developed using previously published JavaScript code prototypes from Google for conducting Spectre-class attacks. It is noted that the researchers managed to prepare working exploits for systems based on Intel and Apple M1 processors, allowing memory reading at a speed of 500 bytes per second with 96% accuracy. It is assumed that the method is also applicable to AMD processors, but a fully functional exploit could not be prepared. <\/p>\n
The attack is applicable to any browsers based on the Chromium engine, including Google Chrome, Microsoft Edge, and Brave. Researchers also believe that the method can be adapted to work with Firefox, but since the Firefox engine is significantly different from Chrome, work on creating a similar exploit has been left for the future. <\/p>\n
To protect against browser-based attacks related to speculative execution, Chrome implements address space segmentation \u2014 sandbox isolation allows JavaScript to operate only with 32-bit pointers and separates handler memory into non-overlapping 4GB heaps. To access the entire address space of the process and bypass the 32-bit limitation, researchers employed a technique called Type Confusion, which forces the JavaScript engine to process an object with an incorrect type, enabling the formation of a 64-bit pointer based on a combination of two 32-bit values. <\/p>\n
The essence of the attack is that when processing a specially crafted malicious object in the JavaScript engine, conditions are created that lead to speculative execution of instructions that access an array. The object is constructed such that the fields controlled by the attackers are placed in an area where a 64-bit pointer is used. Since the type of the malicious object does not match the type of the array being processed, such actions would normally be blocked in Chrome by the code deoptimization mechanism used for array access. To solve this problem, the attack code for Type Confusion is moved into a conditional block 'if' that is not activated under normal conditions but is executed in speculative mode when the processor incorrectly predicts further branching. <\/p>\n
As a result, the processor speculatively accesses the formed 64-bit pointer and rolls back the state after determining an unsuccessful prediction, but the execution traces remain in the shared cache and can be recovered using cache content determination methods through side channels that analyze the change in access times to cached and uncached data. To analyze cache contents under the insufficient accuracy of the timer available in JavaScript, Google proposed a method that deceives the cache eviction strategy used in processors, Tree-PLRU, allowing for a significant increase in the time difference when a value is present in the cache versus when it is not. \n Source: opennet.ru<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"
![\"Play](\"https:\/\/img.youtube.com\/vi\/bP9Hquj5PH4\/hqdefault.jpg\")
\r\n ![\"Play](\"https:\/\/img.youtube.com\/vi\/yz_s4k1zGwA\/hqdefault.jpg\")
\r\n