4 ms·
This article has a bit more information, including suggestions by some that there are indeed exploits active in the wild. https://www.forbes.com/sites/daveywin
by jrochkind1 8y ago
This article has a bit more information, including suggestions by some that there are indeed exploits active in the wild.
https://www.forbes.com/sites/daveywinder/2019/03/07/google-confirms-serious-chrome-security-problem-heres-how-to-fix-it/#f30ea7820029 https://www.forbes.com/sites/daveywinder/2019/03/07/google-c...
> Although information regarding CVE-2019-5786 remains scarce currently, Satnam Narang, a senior research engineer at Tenable, says it is a "Use-After-Free (UAF) vulnerability in FileReader, an application programming interface (API) included in browsers to allow web applications to read the contents of files stored on a user's computer." Some further digging by Catalin Cimpanu over at ZDNet suggests that there are malicious PDF files in the wild that are being used to exploit this vulnerability. "The PDF documents would contact a remote domain with information on the users' device --such as IP address, OS version, Chrome version, and the path of the PDF file on the user's computer" Cimpanu says. These could just be used for tracking purposes, but there is also the potential for more malicious behavior. The 'use-after-free' vulnerability is a memory corruption flaw that carries the risk of escalated privileges on a machine where a threat actor has modified data in memory through exploiting it.
- zenexer 8y agoThat's conflating two unrelated issues. The issue reported by EdgeSpot is much less severe, and a Google engineer hinted that it may not even be a vulnerability. CVE-2019-5786 has nothing to do with PDF files.
- jrochkind1 8y agoya don't gotta downvote me for reposting media coverage! I didn't write the article, if it's wrong, thanks for pointing that out. Just trying to see what there is about it to figure out what's going on, and help people reading skip a step, if you wanna tell us it's wrong, great!