{"id":3621,"date":"2014-01-30T10:19:17","date_gmt":"2014-01-30T15:19:17","guid":{"rendered":"https:\/\/www.kaspersky.com\/blog\/?p=3621"},"modified":"2020-02-26T10:47:09","modified_gmt":"2020-02-26T15:47:09","slug":"listen-chrome","status":"publish","type":"post","link":"https:\/\/www.kaspersky.com\/blog\/listen-chrome\/3621\/","title":{"rendered":"Listen, Chrome\u2026"},"content":{"rendered":"<p>It appears that PCs are not only able to spy on you via cameras, but they\u2019re also able to listen in on you on as well, and in a discreet manner! The only requirements are Google Chrome must be installed on a user\u2019s PC and it must have a microphone.<\/p>\n<p>It comes as no surprise that modern websites are capable of interacting with a wide range of PC peripherals. Of course, a user has to give consent, but that process is usually pretty easy and involves just one click of the \u2018Yes\u2019 button. For instance, in order to upload a photo to a social network profile, one just needs to confirm the pop-up request coming from the website and allow the built-in camera to take a picture. In order to prevent the website from abusing the rights granted by the user, the browser needs to take them away from the webpage. But could it be true that the web resource, without the user\u2019s consent, is continuing to <a href=\"https:\/\/www.kaspersky.com\/blog\/beware-of-webcams\/\" target=\"_blank\" rel=\"noopener nofollow\">control some of the PC functions<\/a>?<\/p>\n<p>Tal Ater, an Israeli software developer, proved that there is a good chance of this happening. The vulnerability he found in the code of the popular Google Chrome browser, if exploited by a cybercriminal, might turn an ordinary PC into the perfect resource for spying on a user. The only thing they have to do is <a href=\"https:\/\/www.kaspersky.com\/blog\/social-engineering-hacking-the-human-os\/\" target=\"_blank\" rel=\"noopener nofollow\">lure the user<\/a> into taking advantage of a voice recognition capability and allow the website to turn on the microphone on a single occasion. From that moment on, the criminal is able to record the sound via microphone, even after the page has been closed. In addition to that, a red blinking indicator on the web browser bar task, which serves as a notice that a recording is in progress, conveniently turns off, leading the user to believe the recording has ended.<\/p>\n<div class=\"pullquote\">The vulnerability found in the code of the popular <a href=\"https:\/\/www.kaspersky.com\/blog\/browser-security-google-chrome\/\" target=\"_blank\" rel=\"noopener nofollow\">Google Chrome<\/a> browser, if exploited by a cybercriminal, might turn an ordinary PC into the perfect resource for spying on a user.<\/div>\n<p>To present his proof of discovery, Ater <a href=\"http:\/\/www.youtube.com\/watch?v=s5D578JmHdU\" target=\"_blank\" rel=\"noopener nofollow\">recorded a 4-minute video<\/a>. It shows perfectly how a user opens and closes a compromised webpage, which uses speech-to-text capabilities, but then continues to record the sound in background mode. The sound data is then sent to Google servers to be converted into text, and then returned to fall into the criminal\u2019s waiting hands.<\/p>\n<p>To make matters worse, the majority of speech-aware websites use a protected https connection. In these cases, Chrome remembers that the page was allowed to use the microphone previously and does not ask for permission again the next time. Moreover, this vulnerability could be tweaked so that certain words are used as triggers to start recording automatically. A ready-made <a href=\"https:\/\/www.kaspersky.com\/blog\/google-chrome-camera\/\" target=\"_blank\" rel=\"noopener nofollow\">tool for spying on people<\/a>!<\/p>\n<p>Curiously enough, Google was aware of the vulnerability back in September. Before <a href=\"https:\/\/threatpost.com\/chrome-eavesdropping-exploit-published\/103798\" target=\"_blank\" rel=\"noopener nofollow\">going public<\/a> with his discovery, Tal Ater contacted the search giant to let them know. In less than two weeks, the company representatives sent him confirmation that the bug had been fixed and the patch was ready. However, it was never published, even four months later. We can only guess why developers of one of the most important browsers reacted so casually.<\/p>\n<p>We recommend users stay alert, or even abstain from voice recognition webpages when using Chrome. As a last resort, you can offload the browser, together with all the bookmarks and processes running \u2013 this way it won\u2019t be able to record anything, or send any data to a cybercriminal.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>It appears that PCs are not only able to spy on you via cameras, but they\u2019re also able to listen in on you on as well, and in a discreet<\/p>\n","protected":false},"author":214,"featured_media":3622,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[5],"tags":[16,93,22],"class_list":{"0":"post-3621","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-news","8":"tag-chrome","9":"tag-cybercriminals","10":"tag-google"},"hreflang":[{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/listen-chrome\/3621\/"},{"hreflang":"en-in","url":"https:\/\/www.kaspersky.co.in\/blog\/listen-chrome\/2875\/"},{"hreflang":"en-ae","url":"https:\/\/me-en.kaspersky.com\/blog\/listen-chrome\/2768\/"},{"hreflang":"en-us","url":"https:\/\/usa.kaspersky.com\/blog\/listen-chrome\/3106\/"},{"hreflang":"en-gb","url":"https:\/\/www.kaspersky.co.uk\/blog\/listen-chrome\/3012\/"},{"hreflang":"ja","url":"https:\/\/blog.kaspersky.co.jp\/listen-chrome\/2491\/"},{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/listen-chrome\/3621\/"},{"hreflang":"en-za","url":"https:\/\/www.kaspersky.co.za\/blog\/listen-chrome\/3621\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/www.kaspersky.com\/blog\/tag\/chrome\/","name":"Chrome"},"_links":{"self":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/3621","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/users\/214"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/comments?post=3621"}],"version-history":[{"count":3,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/3621\/revisions"}],"predecessor-version":[{"id":33028,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/3621\/revisions\/33028"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/media\/3622"}],"wp:attachment":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/media?parent=3621"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/categories?post=3621"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/tags?post=3621"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}