T-Mobile G1 'Android' Smartphone Has Serious Security FlawT-Mobile G1 'Android' Smartphone Has Serious Security Flaw
As if headlines haven't been bad enough lately, reading the <i>New York Times</i>' story on Saturday about the security flaw in Google's Android software didn't help cheer me up very much.
October 26, 2008
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.
About the Author(s)
Hacking Your Digital Identity: How Cybercriminals Can and Will Get Around Your Authentication MethodsOct 26, 2023
Modern Supply Chain Security: Integrated, Interconnected, and Context-DrivenNov 06, 2023
How to Combat the Latest Cloud Security ThreatsNov 06, 2023
Reducing Cyber Risk in Enterprise Email Systems: It's Not Just Spam and PhishingNov 01, 2023
SecOps & DevSecOps in the CloudNov 06, 2023
Passwords Are Passe: Next Gen Authentication Addresses Today's Threats
How to Use Threat Intelligence to Mitigate Third-Party Risk
Concerns Mount Over Ransomware, Zero-Day Bugs, and AI-Enabled Malware
Everything You Need to Know About DNS Attacks
Securing the Remote Worker: How to Mitigate Off-Site Cyberattacks