Google Online Security Blog: julho 2014

Security Blog

The latest news and insights from Google on security and safety on the Internet

Announcing Project Zero

15 de julho de 2014

Posted by Chris Evans, Researcher Herder
Security is a top priority for Google. We've invested a lot in making our products secure, including strong SSL encryption by default for Search, Gmail and Drive, as well as encrypting data moving between our data centers. Beyond securing our own products, interested Googlers also spend some of their time on research that makes the Internet safer, leading to the discovery of bugs like Heartbleed.
The success of that part-time research has led us to create a new, well-staffed team called Project Zero.
You should be able to use the web without fear that a criminal or state-sponsored actor is exploiting software bugs to infect your computer, steal secrets or monitor your communications. Yet in sophisticated attacks, we see the use of "zero-day" vulnerabilities to target, for example, human rights activists or to conduct industrial espionage. This needs to stop. We think more can be done to tackle this problem.
Project Zero is our contribution, to start the ball rolling. Our objective is to significantly reduce the number of people harmed by targeted attacks. We're hiring the best practically-minded security researchers and contributing 100% of their time toward improving security across the Internet.
We're not placing any particular bounds on this project and will work to improve the security of any software depended upon by large numbers of people, paying careful attention to the techniques, targets and motivations of attackers. We'll use standard approaches such as locating and reporting large numbers of vulnerabilities. In addition, we'll be conducting new research into mitigations, exploitation, program analysis—and anything else that our researchers decide is a worthwhile investment.
We commit to doing our work transparently. Every bug we discover will be filed in an external database. We will only report bugs to the software's vendor—and no third parties. Once the bug report becomes public (typically once a patch is available), you'll be able to monitor vendor time-to-fix performance, see any discussion about exploitability, and view historical exploits and crash traces. We also commit to sending bug reports to vendors in as close to real-time as possible, and to working with them to get fixes to users in a reasonable time.
We're hiring. We believe that most security researchers do what they do because they love what they do. What we offer that we think is new is a place to do what you love—but in the open and without distraction. We'll also be looking at ways to involve the wider community, such as extensions of our popular reward initiatives and guest blog posts. As we find things that are particularly interesting, we'll discuss them on our blog, which we hope you'll follow.

Maintaining digital certificate security

8 de julho de 2014

Posted by Adam Langley, Security Engineer
On Wednesday, July 2, we became aware of unauthorized digital certificates for several Google domains. The certificates were issued by the National Informatics Centre (NIC) of India, which holds several intermediate CA certificates trusted by the Indian Controller of Certifying Authorities (India CCA).

The India CCA certificates are included in the Microsoft Root Store and thus are trusted by the vast majority of programs running on Windows, including Internet Explorer and Chrome. Firefox is not affected because it uses its own root store that doesn’t include these certificates.

We are not aware of any other root stores that include the India CCA certificates, thus Chrome on other operating systems, Chrome OS, Android, iOS and OS X are not affected. Additionally, Chrome on Windows would not have accepted the certificates for Google sites because of public-key pinning, although misissued certificates for other sites may exist.

We promptly alerted NIC, India CCA and Microsoft about the incident, and we blocked the misissued certificates in Chrome with a CRLSet push.

On July 3, India CCA informed us that they revoked all the NIC intermediate certificates, and another CRLSet push was performed to include that revocation.

Chrome users do not need to take any action to be protected by the CRLSet updates. We have no indication of widespread abuse and we are not suggesting that people change passwords.

At this time, India CCA is still investigating this incident. This event also highlights, again, that our Certificate Transparency project is critical for protecting the security of certificates in the future.

Update Jul 9: India CCA informed us of the results of their investigation on July 8. They reported that NIC’s issuance process was compromised and that only four certificates were misissued; the first on June 25. The four certificates provided included three for Google domains (one of which we were previously aware of) and one for Yahoo domains. However, we are also aware of misissued certificates not included in that set of four and can only conclude that the scope of the breach is unknown.

The intermediate CA certificates held by NIC were revoked on July 3, as noted above. But a root CA is responsible for all certificates issued under its authority. In light of this, in a future Chrome release, we will limit the India CCA root certificate to the following domains and subdomains thereof in order to protect users:

gov.in
nic.in
ac.in
rbi.org.in
bankofindia.co.in
ncode.in
tcs.co.in

Marcadores

Archive

2024
- dez.
- nov.
- out.
- set.
- ago.
- jul.
- jun.
- mai.
- abr.
- mar.
- fev.
- jan.

2023
- dez.
- nov.
- out.
- set.
- ago.
- jul.
- jun.
- mai.
- abr.
- mar.
- fev.
- jan.

2022
- dez.
- nov.
- out.
- set.
- ago.
- jul.
- jun.
- mai.
- abr.
- mar.
- fev.
- jan.

2021
- dez.
- nov.
- out.
- set.
- ago.
- jul.
- jun.
- mai.
- abr.
- mar.
- fev.
- jan.

2020
- dez.
- nov.
- out.
- set.
- ago.
- jul.
- jun.
- mai.
- abr.
- mar.
- fev.
- jan.

2019
- dez.
- nov.
- out.
- set.
- ago.
- jul.
- jun.
- mai.
- abr.
- mar.
- fev.
- jan.

2018
- dez.
- nov.
- out.
- set.
- ago.
- jul.
- jun.
- mai.
- abr.
- mar.
- fev.
- jan.

2017
- dez.
- nov.
- out.
- set.
- jul.
- jun.
- mai.
- abr.
- mar.
- fev.
- jan.

2016
- dez.
- nov.
- out.
- set.
- ago.
- jul.
- jun.
- mai.
- abr.
- mar.
- fev.
- jan.

2015
- dez.
- nov.
- out.
- set.
- ago.
- jul.
- jun.
- mai.
- abr.
- mar.
- fev.
- jan.

2014
- dez.
- nov.
- out.
- set.
- ago.
- jul.
- jun.
- abr.
- mar.
- fev.
- jan.

2013
- dez.
- nov.
- out.
- ago.
- jun.
- mai.
- abr.
- mar.
- fev.
- jan.

2012
- dez.
- set.
- ago.
- jun.
- mai.
- abr.
- mar.
- fev.
- jan.

2011
- dez.
- nov.
- out.
- set.
- ago.
- jul.
- jun.
- mai.
- abr.
- mar.
- fev.

2010
- nov.
- out.
- set.
- ago.
- jul.
- mai.
- abr.
- mar.

2009
- nov.
- out.
- ago.
- jul.
- jun.
- mar.

2008
- dez.
- nov.
- out.
- ago.
- jul.
- mai.
- fev.

2007
- nov.
- out.
- set.
- jul.
- jun.
- mai.

Feed

Give us feedback in our Product Forums.

Google
Privacy
Terms