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

8/19/2008
08:44 PM
George V. Hulme
George V. Hulme
Commentary
50%
50%

As Google Android SDK Hits Street, Android Security Team Braces

It's been a big week for the Android phone platform. Most important, the Federal Communications Commission gave the all clear to the first Android-powered handset, which will be built by High Tech Computer and is currently expected to be called the Dream. Additionally, Google released an updated versi

It's been a big week for the Android phone platform. Most important, the Federal Communications Commission gave the all clear to the first Android-powered handset, which will be built by High Tech Computer and is currently expected to be called the Dream. Additionally, Google released an updated version of its SDK.This version of the SDK, version 0.9, Google says, is very close to what the final SDK will look like. While this is all good news for anyone who has yet to buy an iPhone and sign up for a lengthy AT&T contract, it also means that more security researchers, if they haven't already started, will begin hammering away for any existing security-related vulnerabilities. It's what they do, and in the long run, their work improves the quality of software.

Google knows this, and already is bracing for the storm. This is from an e-mail the Android Security Team posted to the popular Full Disclosure mailing list yesterday:

As you may expect, building and maintaining a secure mobile platform 
is a difficult task. The Android platform team has put a great deal 
of work into trying to design a platform that balances our goal of 
open development and user choice with the unique challenges of 
securing a consumer-focused mobile system. While we have found and 
fixed many of our own bugs as well as flaws in other open source 
projects, we realize that the discovery of additional security issues 
in a system this large and complex is inevitable. That is why we 
would like to introduce ourselves today and let the security research 
community know how they can reach out and work with us.

The note then went on to explain how Google would appreciate security researchers go about reporting their finds. Not surprisingly, the Google Android Security Team favors reasonable disclosure practices, which is to say researchers would contact Google with the flaws they find, give Google a chance to fix the flaw, and then the flaw and patch are announced the same day with kudos going to the security researchers who found the problem.

Responsible disclosure is the best way to go for everyone. Whenever security flaws are randomly dumped out publicly, users get attacked and vendors are forced to rush shoddy patches out the door. With responsible disclosure, the flaws get fixed, and we all have a chance to patch our systems.

And Google is taking the right approach here, to try to keep open lines of communication with the security research community. Let's hope this communication goes both ways.

 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/10/2020
Researcher Finds New Office Macro Attacks for MacOS
Curtis Franklin Jr., Senior Editor at Dark Reading,  8/7/2020
Lock-Pickers Face an Uncertain Future Online
Seth Rosenblatt, Contributing Writer,  8/10/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-17505
PUBLISHED: 2020-08-12
Artica Web Proxy 4.30.000000 allows an authenticated remote attacker to inject commands via the service-cmds parameter in cyrus.php. These commands are executed with root privileges via service_cmds_peform.
CVE-2020-17506
PUBLISHED: 2020-08-12
Artica Web Proxy 4.30.00000000 allows remote attacker to bypass privilege detection and gain web backend administrator privileges through SQL injection of the apikey parameter in fw.login.php.
CVE-2020-2035
PUBLISHED: 2020-08-12
When SSL/TLS Forward Proxy Decryption mode has been configured to decrypt the web transactions, the PAN-OS URL filtering feature inspects the HTTP Host and URL path headers for policy enforcement on the decrypted HTTPS web transactions but does not consider Server Name Indication (SNI) field within ...
CVE-2020-5415
PUBLISHED: 2020-08-12
Concourse, versions prior to 6.3.1 and 6.4.1, in installations which use the GitLab auth connector, is vulnerable to identity spoofing by way of configuring a GitLab account with the same full name as another user who is granted access to a Concourse team. GitLab groups do not have this vulnerabilit...
CVE-2020-6653
PUBLISHED: 2020-08-12
Eaton's Secure connect mobile app v1.7.3 & prior stores the user login credentials in logcat file when user create or register the account on the Mobile app. A malicious app or unauthorized user can harvest the information and later on can use the information to monitor and control the user's ac...