Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Risk

9/3/2008
08:07 PM
Keith Ferrell
Keith Ferrell
Commentary
50%
50%

Google Chrome Security Risks Already Announced

Barely a day after Google's new browser was released, Chrome is showing some scratches: researchers have pointed out known security vulnerabilities that can put users at risk of malicious exploits.

Barely a day after Google's new browser was released, Chrome is showing some scratches: researchers have pointed out known security vulnerabilities that can put users at risk of malicious exploits.The Chrome security flaws identified this afternoon include known WebKit (the open source engine the browser is constructed around) vulnerabilities that, combined with a Java bug, can result in downloads of executable malicious files.

Other security researchers note there are ways to crash Chrome via malicious links, possibly without user input.

Early days for Chrome yet, and very early for the risk assessments and vulnerability audits to be anywhere near complete: we'll all be hearing plenty more about these -- and, one hopes, patches and fixes for them -- in the next few days.

For now it's worth reminding yourself and your employees that Chrome is still in beta, a work in progress that, for all of its promise, and especially all of its buzz, should be used carefully (if at all) in the small and midsize business workplace.

Your call of course, but it's a call you should make, one way or another, before those tech-happy members of your non-IT staff get too many copies of Chrome, with its now-known vulnerabilities, running on too many of your company's systems.

More From bMighty: Roundup: Google Chrome

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 5/28/2020
Stay-at-Home Orders Coincide With Massive DNS Surge
Robert Lemos, Contributing Writer,  5/27/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Can you smell me now?
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-11844
PUBLISHED: 2020-05-29
There is an Incorrect Authorization vulnerability in Micro Focus Service Management Automation (SMA) product affecting version 2018.05 to 2020.02. The vulnerability could be exploited to provide unauthorized access to the Container Deployment Foundation.
CVE-2020-6937
PUBLISHED: 2020-05-29
A Denial of Service vulnerability in MuleSoft Mule CE/EE 3.8.x, 3.9.x, and 4.x released before April 7, 2020, could allow remote attackers to submit data which can lead to resource exhaustion.
CVE-2020-7648
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.72.2 are vulnerable to Arbitrary File Read. It allows arbitrary file reads for users who have access to Snyk's internal network by appending the URL with a fragment identifier and a whitelisted path e.g. `#package.json`
CVE-2020-7650
PUBLISHED: 2020-05-29
All versions of snyk-broker after 4.72.0 including and before 4.73.1 are vulnerable to Arbitrary File Read. It allows arbitrary file reads to users with access to Snyk's internal network of any files ending in the following extensions: yaml, yml or json.
CVE-2020-7654
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.73.1 are vulnerable to Information Exposure. It logs private keys if logging level is set to DEBUG.