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

10/26/2008
11:25 PM
George V. Hulme
George V. Hulme
Commentary
50%
50%

T-Mobile G1 'Android' Smartphone Has Serious Security Flaw

As if headlines haven't been bad enough lately, reading the New York Times' story on Saturday about the security flaw in Google's Android software didn't help cheer me up very much.

As if headlines haven't been bad enough lately, reading the New York Times' story on Saturday about the security flaw in Google's Android software didn't help cheer me up very much.John Markoff, over at the New York Times, wrote an excellent account of a flaw in the new T-Mobile G1 smartphone. This flaw looks particularly nasty, and according to Markoff's story, is the result of Google failing to use the most recent versions of the open source components that form Android's foundation.

The risk in the Google design, according to Mr. Miller [note: security researcher Charles A. Miller], who is a principal security analyst at Independent Security Evaluators in Baltimore, lies in the danger from within the Web browser partition in the phone. It would be possible, for example, for an intruder to install software that would capture keystrokes entered by the user when surfing to other Web sites. That would make it possible to steal identity information or passwords.

That's a nasty one. But it seems that while Miller told Google of the flaw, he also disclosed its existence before Google had a chance to patch. Miller explains his reasoning to Markoff:

Mr. Miller said he was withholding technical details, but said he felt that consumers had a right to know that products had shortcomings.

First: if you don't know that products have "shortcomings," you probably lack the IQ necessary to dial the G1.

Didn't we experiment with this partial-advance disclosure earlier this year with the now-famous DNS flaw which was announced sans-technical details by Dan Kaminsky? We all know it didn't take long for other security experts to figure out the nature of the flaw, and the information got released before everyone had time to patch. Despite Kaminsky's best intentions, the situation went into a nasty flat-spin that lasted for weeks.

Thankfully, since the T-Mobile G1 doesn't come remotely close in importance to the Internet's DNS, we're not in for a repeat of the same magnitude. But it does show the debate on the proper disclosure of vulnerabilities just isn't going to die.

No. The disclosure debate is like the maniacal killer in a bad horror flick: he just keeps lurching out at you at every turn.

 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/3/2020
Pen Testers Who Got Arrested Doing Their Jobs Tell All
Kelly Jackson Higgins, Executive Editor at Dark Reading,  8/5/2020
Browsers to Enforce Shorter Certificate Life Spans: What Businesses Should Know
Kelly Sheridan, Staff Editor, Dark Reading,  7/30/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
The Changing Face of Threat Intelligence
The Changing Face of Threat Intelligence
This special report takes a look at how enterprises are using threat intelligence, as well as emerging best practices for integrating threat intel into security operations and incident response. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-17366
PUBLISHED: 2020-08-05
An issue was discovered in NLnet Labs Routinator 0.1.0 through 0.7.1. It allows remote attackers to bypass intended access restrictions or to cause a denial of service on dependent routing systems by strategically withholding RPKI Route Origin Authorisation ".roa" files or X509 Certificate...
CVE-2020-9036
PUBLISHED: 2020-08-05
Jeedom through 4.0.38 allows XSS.
CVE-2020-15127
PUBLISHED: 2020-08-05
In Contour ( Ingress controller for Kubernetes) before version 1.7.0, a bad actor can shut down all instances of Envoy, essentially killing the entire ingress data plane. GET requests to /shutdown on port 8090 of the Envoy pod initiate Envoy's shutdown procedure. The shutdown procedure includes flip...
CVE-2020-15132
PUBLISHED: 2020-08-05
In Sulu before versions 1.6.35, 2.0.10, and 2.1.1, when the "Forget password" feature on the login screen is used, Sulu asks the user for a username or email address. If the given string is not found, a response with a `400` error code is returned, along with a error message saying that th...
CVE-2020-7298
PUBLISHED: 2020-08-05
Unexpected behavior violation in McAfee Total Protection (MTP) prior to 16.0.R26 allows local users to turn off real time scanning via a specially crafted object making a specific function call.