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
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 7/2/2020
Ripple20 Threatens Increasingly Connected Medical Devices
Kelly Sheridan, Staff Editor, Dark Reading,  6/30/2020
DDoS Attacks Jump 542% from Q4 2019 to Q1 2020
Dark Reading Staff 6/30/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
The Threat from the Internetand What Your Organization Can Do About It
The Threat from the Internetand What Your Organization Can Do About It
This report describes some of the latest attacks and threats emanating from the Internet, as well as advice and tips on how your organization can mitigate those threats before they affect your business. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-9498
PUBLISHED: 2020-07-02
Apache Guacamole 1.1.0 and older may mishandle pointers involved inprocessing data received via RDP static virtual channels. If a userconnects to a malicious or compromised RDP server, a series ofspecially-crafted PDUs could result in memory corruption, possiblyallowing arbitrary code to be executed...
CVE-2020-3282
PUBLISHED: 2020-07-02
A vulnerability in the web-based management interface of Cisco Unified Communications Manager, Cisco Unified Communications Manager Session Management Edition, Cisco Unified Communications Manager IM & Presence Service, and Cisco Unity Connection could allow an unauthenticated, remote attack...
CVE-2020-5909
PUBLISHED: 2020-07-02
In versions 3.0.0-3.5.0, 2.0.0-2.9.0, and 1.0.1, when users run the command displayed in NGINX Controller user interface (UI) to fetch the agent installer, the server TLS certificate is not verified.
CVE-2020-5910
PUBLISHED: 2020-07-02
In versions 3.0.0-3.5.0, 2.0.0-2.9.0, and 1.0.1, the Neural Autonomic Transport System (NATS) messaging services in use by the NGINX Controller do not require any form of authentication, so any successful connection would be authorized.
CVE-2020-5911
PUBLISHED: 2020-07-02
In versions 3.0.0-3.5.0, 2.0.0-2.9.0, and 1.0.1, the NGINX Controller installer starts the download of Kubernetes packages from an HTTP URL On Debian/Ubuntu system.