Notebookcheck
, , , , , ,
search relation.
, , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,
 

Google needed more than three years to patch a flaw in Chrome for Android

Google Chrome for Android still has three-year-old bugs, fix coming soon
Google Chrome for Android still has three-year-old bugs
Back in May 2015, a serious flaw in Chrome for Android that exposed various bits of sensitive information was discovered. This security issue was ignored by Google for more than three years, but now the tech giant is finally taking care of it. Unfortunately, a final fix for this vulnerability is not available yet.
Codrut Nistor,
, , , , , ,
search relation.
, , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,
 

On the last day of May 2015, a report concerning a bug discovered in Chrome 43 on Android 5.1 Lollipop was published here. Its name — Chrome on Android reveals the exact model and OS version of the device used via user agent — is suggestive and Google engineers should have been worried about the possible effects of this vulnerability. However, it seems that they still need some time to take care of it properly.

At the end of September 2015, Nightwatch Cybersecurity published an in-depth research article concerning the aforementioned bug. According to a much more recent report by the same security organization, Google came up with a partial fix in October 2018. Back then, Chrome 70 for Android removed the firmware build information from the set of exposed information. Unfortunately, the device model number can still be accessed by using the same method.

Since we are already in 2019, we can only hope that Google will finally address this flaw before it gets as old as four years. Obviously, some might not consider it that much of a hassle, but it's always better to know that a certain threat — small or not-so-small — has been ironed out. 

Do you think that this kind of issue should be considered a minor one or not? Is Google doing enough to keep our Android devices safe? Feel free to let us know what you think in the comments section below, as usual.

Source(s)

static version load dynamic
Loading Comments
Comment on this article
, , , , , ,
search relation.
, , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,
 
Codrut Nistor
Codrut Nistor - Senior Tech Writer - 5461 articles published on Notebookcheck since 2013
In my early school days, I hated writing and having to make up stories. A decade later, I started to enjoy it. Since then, I published a few offline articles and then I moved to the online space, where I contributed to major websites that are still present online as of 2021 such as Softpedia, Brothersoft, Download3000, but I also wrote for multiple blogs that have disappeared over the years. I've been riding with the Notebookcheck crew since 2013 and I am not planning to leave it anytime soon. In love with good mechanical keyboards, vinyl and tape sound, but also smartphones, streaming services, and digital art.
Please share our article, every link counts!
> Notebook / Laptop Reviews and News > News > News Archive > Newsarchive 2019 01 > Google needed more than three years to patch a flaw in Chrome for Android
Codrut Nistor, 2019-01- 3 (Update: 2019-01- 3)