Monday, 8 July 2013

Google Australia offices vulnerable to remote attack

Summary: Two security researchers have had to point out old and unpatched vulnerabilities in the software responsible for Google's building management systems to get the web giant to take action.

For a period of time, hackers could have turned up the heat at Google's Australian offices, with the systems responsible for controlling the heating, ventilation, and air conditioning being vulnerable to take-over.
Its Australian offices at Wharf 7, Pyrmont, Sydney, is looked after by a building management system made by Tridium. Building management systems like these regulate temperatures, air conditioning zones, and other such building elements by responding to building or environmental inputs, such as the temperature measured from a thermostat or the time of day, allowing buildings to be "warmed up" prior to employees first entering.
However, these back-end systems can be connected to and accessed from the internet. ZDNet found several Australian businesses last year that were running the same systems from Tridium without any form of authentication, potentially allowing anyone to shut down any of the connected building control systems without permission.
While Google's own instance of the system did implement some level of authentication, researchers Billy Rios and Terry McCorkle from information security company Cylance were able to bypass these restrictions easily, as the system was not kept up to date. Rios and McCorkle had previously contacted Tridium regarding a directory traversal vulnerability, which could allow access to restricted files within the management system.
Typically, the public-facing "root" of a site corresponds to a particular directory on a server. For example, www.example.com/ might correspond to /usr/home/public_html. However, when incorrectly configured, the web server may not recognise that it should not honour requests to traverse above this folder. Hence, navigating to www.example.com/../ could expose the /usr/home directory, or www.example.com/../../../ could expose the root file system, if the web server has permissions to view these directories.
This vulnerability was pointed out to Tridium by Rios and McCorkle in July 2012, and the company issued an alert to its customers to take precautionary steps. It released a security patch to further address the issue in August, and noted in a security alert that a specific file, config.bog, could be a security risk if attackers were able to access it.
A second patch against directory traversal was released in February this year, indicating that the problem had not been fully resolved.
The config.bog file was the prime target of Rios and McCorkle's infiltration into the system, as it contains the usernames and hashed passwords for all device users. As Google's implementation of Tridium's software was not kept up to date, Rios and McCorkle were able to exploit the directory traversal vulnerability, retrieve the config.bog file, and extract the hash of the administrator password.
The password itself was easily cracked by Rios and McCorkle, as Tridium's system does not use any form of salting to increase password complexity. The fact that Rios and McCorkle were able to reverse the hash also indicates that the password used on the system would have been weak.
From here, Rios and McCorkle had full run of Google's building management system, and stated that they could have rooted the device. This would provide the pair of researchers with access to a machine from which they could conduct further attacks.
Google has disagreed with their claim, with a Google spokesperson telling ZDNet that the device accessed by the researchers was capable only of managing the air conditioning system and nothing more.
Rios and McCorkle did not root the device, but instead reported the issue to the company via its Vulnerability Rewards Program; however, the issue was not eligible for a reward. According to the researchers, the system has now been pulled offline.
A Google Australia spokesperson said Google is grateful when researchers report their findings, and that it has taken appropriate action to resolve the issue.

 

facebook.com/whitehat

If you are a security researcher, please review our responsible disclosure policy before reporting any vulnerabilities. If you are not a security researcher, visit the Facebook Security Page for assistance.
If you believe you have found a security vulnerability on Facebook, we encourage you to let us know right away. We will investigate all legitimate reports and do our best to quickly fix the problem.
Responsible Disclosure Policy
If you give us a reasonable time to respond to your report before making any information public and make a good faith effort to avoid privacy violations, destruction of data and interruption or degradation of our service during your research, we will not bring any lawsuit against you or ask law enforcement to investigate you.
Bug Bounty Info To show our appreciation for our security researchers, we offer a monetary bounty for certain qualifying security bugs. Here is how it works:

Eligibility

To qualify for a bounty, you must:
  • Adhere to our Responsible Disclosure Policy (above)
  • Be the first person to responsibly disclose the bug
  • Report a bug that could compromise the integrity of Facebook user data, circumvent the privacy protections of Facebook user data, or enable access to a system within the Facebook infrastructure, such as:
    • Cross-Site Scripting (XSS)
    • Cross-Site Request Forgery (CSRF/XSRF)
    • Broken Authentication (including Facebook OAuth bugs)
    • Circumvention of our Platform/Privacy permission models
    • Remote Code Execution
    • Privilege Escalation
    • Provisioning Errors
  • Please use a test account instead of a real account when investigating bugs. When you are unable to reproduce a bug with a test account, it is acceptable to use a real account, except for automated testing. Do not interact with other accounts without the consent of their owners.
  • Reside in a country not under any current U.S. Sanctions (e.g., North Korea, Libya, Cuba, etc.)
Our security team will assess each bug to determine if it qualifies.

Rewards

  • Our minimum reward is $500 USD
  • There is no maximum reward: each bug is awarded a bounty based on its severity and creativity
  • Only 1 bounty per security bug will be awarded

Exclusions

The following bugs are not eligible for a bounty (and we do not recommend testing for these):
  • Security bugs in third-party applications (e.g., http://apps.facebook.com/[app_name])
  • Security bugs in third-party websites that integrate with Facebook
  • Denial of Service Vulnerabilities
  • Spam or Social Engineering techniques
  • Acquisitions have a 3 month delay before we accept submissions.

‘Yahoo Hack India’ event to begin on 13 July in Hyderabad

Programmers, developers, designers from across the industry and students from top technical universities in India will gather at Hyderabad for a two-day hacking event.
Over 1,000 developers from across 20 states had signed up to participate in the sixth edition of “Yahoo! Hack India” from July 13, of which 250 best hackers have been selected after an entry-level coding challenge.
“These hackers will now participate in the two-day event which brings forth a series of technical workshops, followed by a nonstop 24-hour coding Hackathon on July 13 and 14,” a statement said.
For the first time, Yahoo! Hack India is being organised in cyber city Hyderabad. This will be Yahoo!’s first hack event in India hosted outside Bangalore, where Yahoo! has its second largest research and development centre.
Reuters
Yahoo logo is seen in this file photo. Reuters
Due to overwhelming response from developers across India in the last five years, Yahoo! had decided to expand this hack events to cover more Indian cities over the next few years.
“This year will see two external hack events by Yahoo! in India, one in Hyderabad and another in Bangalore later in this year. The event brings together programmers, developers, designers from across the industry, start ups and students from the top technical universities,” it said.
“Hackers team up to turn their ideas into a working prototype, or hack, as it’s called in just 24 hours. It gives developers a chance to work together and build applications and product ideas from scratch using market-leading technologies from Yahoo! as well as other technologies, to develop something cool that can potentially solve a real-world problem that impacts Internet users,” it said.
The two-day event involves a hacking competition using a great collection of new web tools, services and APIs (Application Programmable Interface), as well as data from around the web.
Yahoo! Open Hack was started as an internal event in 2006 at Yahoo! headquarters in Sunnyvale, US with an aim to bring the Yahoo! developers together. So far, Open Hack has been hosted in seven countries with representation from over 30 countries.
The first Open Hack in India was hosted way back in 2007, which was attended by 180 developers from in and around Bangalore.