{"id":3903,"date":"2015-04-16T02:42:41","date_gmt":"2015-04-15T18:42:41","guid":{"rendered":"https:\/\/www.darknet.org.uk\/?p=3903"},"modified":"2015-09-09T19:36:38","modified_gmt":"2015-09-09T11:36:38","slug":"google-chrome-42-stomps-a-lot-of-bugs-disables-java-by-default","status":"publish","type":"post","link":"https:\/\/www.darknet.org.uk\/2015\/04\/google-chrome-42-stomps-a-lot-of-bugs-disables-java-by-default\/","title":{"rendered":"Google Chrome 42 Stomps A LOT Of Bugs & Disables Java By Default"},"content":{"rendered":"

Ah finally, the end of NPAPI is coming – a relic from the Netscape era the Netscape Plugin API causes a lot of instability in Chrome and security issues. It means Java is now disabled by default along with other NPAPI based plugins in Google Chrome 42.<\/p>\n

Chrome will be removing support for NPAPI totally in Chrome 45.<\/p>\n

\"Google<\/p>\n

Other than that, they have also squashed 45 security issues and vulnerabilities, including some quite serious ones. And many, a product of their Bug Bounty program<\/a>.<\/p>\n

Google announced on Tuesday the availability of Chrome 42 for Windows, Mac and Linux. The latest release addresses a total of 45 security issues and removes NPAPI support.<\/p>\n

Judging by the bug bounties paid out by Google, the most serious vulnerability fixed in Chrome 42 is a cross-origin bypass flaw in the HTML parser (CVE-2015-1235). The discovery of this high severity bug earned an anonymous researcher $7,500.<\/p>\n

The list of high severity vulnerabilities also includes a type confusion in V8 (CVE-2015-1242) reported by Cole Forrester of Onshape, a use-after-free in IPC (CVE-2015-1237) reported by Khalil Zhani, and an out-of-bounds write bug in the Skia graphics engine (CVE-2015-1238) identified by cloudfuzzer.<\/p>\n

The medium severity security issues reported by external researchers are a cross-origin-bypass in the Blink web browser engine, an out-of-bounds read in WebGL, a use-after-free in PDFium, a tap-jacking flaw, an HSTS bypass in WebSockets, an out-of-bounds read in Blink, scheme issues in OpenSearch, and a SafeBrowsing bypass.<\/p>\n

The researchers who contributed to making Chrome more secure have been awarded a total of $21,500, according to a blog post published by Google. However, the total amount could be higher since there are some vulnerability reports that haven\u2019t gone through the search giant\u2019s reward panel.<\/p><\/blockquote>\n