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.

Cloud

5/15/2015
04:10 PM
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
100%
0%

Polish Security Firm Discloses Unpatched Security Flaws in Google App Engine

Google was given enough time to respond researcher says.

Google’s Project Zero vulnerability research group has drawn some flak recently for its practice of publicly disclosing security flaws in software from other vendors after a 90-day notice period, regardless of whether patches are available or not.

Friday, the company may have gotten a small taste of its own medicine when Polish firm Security Explorations Friday released details on several unpatched vulnerabilities in Google’s cloud software after the Internet giant allegedly failed to respond in a timely manner to the issue.

The vulnerabilities in Google’s App Engine (GAE) software include three complete Java sandbox escapes that could be used to gather a lot of information on the Java Runtime Environment sandbox itself. “They also seem to be a potentially good starting point to proceed with attacks against the OS sandbox and RPC services visible to the sandboxed Java environment,” Adam Gowdiak, CEO of Security Explorations said in emailed comments to Dark Reading.

In addition to the flaws, Security Explorations also released proof of concept code showing how the vulnerabilities can be exploit to bypass the Java security sandbox in GAE.

Google’s App Engine is a hosted service for enterprises seeking to run and maintain applications in the cloud.

This is the second time in less than six months that Security Explorations has uncovered holes in the technology. In December, the company disclosed a total of 31 security issues in the software, including 22 that allowed an escape from the Java security sandbox.

Google patched those flaws by mid-March, Gowdiak said. Following that, between March and April, Security Explorations reported an additional 10 issues to Google, of which seven were publicly disclosed today, he added.

“The security issues published today need to be combined together in order to conduct a successful attack. In that context, it's difficult to point to a single one that's the most serious,” Gowdiak said. The Java security sandbox escape exploit was the most that Security Explorations could achieve given the constraints under which it conducted the vulnerability research on GAE, he said.

For Google, the disclosures by Security Explorations have become a sort of test of its own tolerance for bug disclosures for which no patches are immediately available. The disclosure also focuses attention once again on the issue of responsible bug disclosure practices, especially at a time when enterprises need all the protection they can from software vendors.

Many security researchers and vendors acknowledge that the safest way to publicly disclose bugs in software products is after the vendor has had a chance to fix it. But there is considerable debate on just how much notice is reasonable enough for a vendor to address the issue.

Google itself has maintained that a 90-day window is more than enough time for a fix. But some within the industry have been irritated by the company’s refusal—till recently at least—to budge from that deadline.

In January, Microsoft’s senior director of Trustworthy Computing Chris Betz, raked Google through the coals for publicly releasing information on a flaw in a Microsoft product, just two days before a scheduled Patch Tuesday fix for it.

Although sticking to a deadline is good policy, Google’s decision to go public with the flaw despite knowing about the fix, “feels less like principles and more like a “gotcha,” with customers the ones who may suffer as a result,” Betz had noted. Contrary to perception, publicly releasing information on a flaw without context or further protections, “unduly pressures an already complicated technical environment,” he had said.

Following the criticism, Google loosened its disclosure policy a bit and now gives vendors a grace period beyond 90 days in certain cases.

Google did not respond to a request for comment.

It’s unclear how the company’s views the latest disclosures by Security Explorations. Back in December, the security firm claimed Google initially suspended its GAE account following the disclosures. Later, the company announced that it had received a reward of  $50,000 from Google for finding the bugs.

This time around, Gowdiak says he gave Google three weeks to confirm or deny the reported flaws. “They were fully documented and accompanied by Proof of Concept codes,” he said.

Gowdiak said Security Explorations does not follow a strict rule for vulnerability disclosures. “If a vulnerability is confirmed by a vendor and we are provided with status updates regarding the patching process, we usually wait …until the patches are released. “

Jai Vijayan is a seasoned technology reporter with over 20 years of experience in IT trade journalism. He was most recently a Senior Editor at Computerworld, where he covered information security and data privacy issues for the publication. Over the course of his 20-year ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Oldest First  |  Newest First  |  Threaded View
The Problem with Proprietary Testing: NSS Labs vs. CrowdStrike
Brian Monkman, Executive Director at NetSecOPEN,  7/19/2019
How Attackers Infiltrate the Supply Chain & What to Do About It
Shay Nahari, Head of Red-Team Services at CyberArk,  7/16/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Building and Managing an IT Security Operations Program
As cyber threats grow, many organizations are building security operations centers (SOCs) to improve their defenses. In this Tech Digest you will learn tips on how to get the most out of a SOC in your organization - and what to do if you can't afford to build one.
Flash Poll
The State of IT Operations and Cybersecurity Operations
The State of IT Operations and Cybersecurity Operations
Your enterprise's cyber risk may depend upon the relationship between the IT team and the security team. Heres some insight on what's working and what isn't in the data center.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-10102
PUBLISHED: 2019-07-22
The Linux Foundation ONOS 1.15.0 and ealier is affected by: Improper Input Validation. The impact is: The attacker can remotely execute any commands by sending malicious http request to the controller. The component is: Method runJavaCompiler in YangLiveCompilerManager.java. The attack vector is: ne...
CVE-2019-10102
PUBLISHED: 2019-07-22
Frog CMS 1.1 is affected by: Cross Site Scripting (XSS). The impact is: Cookie stealing, Alert pop-up on page, Redirecting to another phishing site, Executing browser exploits. The component is: Snippets.
CVE-2019-10102
PUBLISHED: 2019-07-22
Ilias 5.3 before 5.3.12; 5.2 before 5.2.21 is affected by: Cross Site Scripting (XSS) - CWE-79 Type 2: Stored XSS (or Persistent). The impact is: Execute code in the victim's browser. The component is: Assessment / TestQuestionPool. The attack vector is: Cloze Test Text gap (attacker) / Corrections ...
CVE-2019-9959
PUBLISHED: 2019-07-22
The JPXStream::init function in Poppler 0.78.0 and earlier doesn't check for negative values of stream length, leading to an Integer Overflow, thereby making it possible to allocate a large memory chunk on the heap, with a size controlled by an attacker, as demonstrated by pdftocairo.
CVE-2019-4236
PUBLISHED: 2019-07-22
A IBM Spectrum Protect 7.l client backup or archive operation running for an HP-UX VxFS object is silently skipping Access Control List (ACL) entries from backup or archive if there are more than twelve ACL entries associated with the object in total. As a result, it could allow a local attacker to ...