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/8/2008
01:10 PM
Keith Ferrell
Keith Ferrell
Commentary
50%
50%

UPDATE: Some Google Chrome Problems Patched, Blended Threat Vulnerability Remains

Update Google Chrome now! (We tell you how below.) A buffer overflow vulnerability in the new browser has been identified and patched but, contrary to early reports, the blended WebKit/Java vulnerability has NOT been patched yet.

Update Google Chrome now! (We tell you how below.) A buffer overflow vulnerability in the new browser has been identified and patched but, contrary to early reports, the blended WebKit/Java vulnerability has NOT been patched yet.The buffer overflow issue results from using too-long filenames in your save-as file downloads, according to a post from Vietnamese security company Bach Koa Internetwork Security.

Chrome's developers have released an upgrade of the browser that repairs this problem.

As far as the WebKit/Java blended threat vulnerability discussed here (and everyplace else) last week, reports vary with some early statements, including this blog (and my apologies for that) reporting that the problem was patched. Evidently it's not.

Note to Google: how about posting change-logs and other update details so people know immediately what is and isn't fixed.

While we wait for the blended threat patch, the buffer overflow fix is available by updating Chrome. Do so by:

1. Click on the wrench in the browser's upper right corner

2. Click on "About Google Chrome" in the dropdown Menu

3. Wait while Chrome checks your browser and, if necessary, updates it.

The version you should be running to have the repairs in place is 0.2.149.29.

Again, my apologies for the earlier inaccuracy regarding the breadth of the patch and the vulnerabilities it addresses.

More From bMighty: Roundup: Google Chrome

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Commentary
What the FedEx Logo Taught Me About Cybersecurity
Matt Shea, Head of Federal @ MixMode,  6/4/2021
Edge-DRsplash-10-edge-articles
A View From Inside a Deception
Sara Peters, Senior Editor at Dark Reading,  6/2/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-23394
PUBLISHED: 2021-06-13
The package studio-42/elfinder before 2.1.58 are vulnerable to Remote Code Execution (RCE) via execution of PHP code in a .phar file. NOTE: This only applies if the server parses .phar files as PHP.
CVE-2021-34682
PUBLISHED: 2021-06-12
Receita Federal IRPF 2021 1.7 allows a man-in-the-middle attack against the update feature.
CVE-2021-31811
PUBLISHED: 2021-06-12
In Apache PDFBox, a carefully crafted PDF file can trigger an OutOfMemory-Exception while loading the file. This issue affects Apache PDFBox version 2.0.23 and prior 2.0.x versions.
CVE-2021-31812
PUBLISHED: 2021-06-12
In Apache PDFBox, a carefully crafted PDF file can trigger an infinite loop while loading the file. This issue affects Apache PDFBox version 2.0.23 and prior 2.0.x versions.
CVE-2021-32552
PUBLISHED: 2021-06-12
It was discovered that read_file() in apport/hookutils.py would follow symbolic links or open FIFOs. When this function is used by the openjdk-16 package apport hooks, it could expose private data to other local users.