The discovery of the
Log4Shell vulnerability has set the internet on fire. Similar to
shellshock and
heartbleed, Log4Shell is just the latest catastrophic vulnerability in
software that runs the internet. Our mission as the Google Open Source Security Team is to secure the open source libraries the world depends on, such as Log4j. One of our capabilities in this space is OSS-Fuzz, a free fuzzing service that is used by over 500 critical open source projects and has found more than
7,000 vulnerabilities in its lifetime.
We want to empower open source developers to secure their code on their own. Over the next year we will work on better automated detection of non-memory corruption vulnerabilities such as Log4Shell. We have started this work by partnering with the security company
Code Intelligence to
provide continuous fuzzing for Log4j, as part of OSS-Fuzz. Also as part of this partnership, Code-Intelligence improved their
Jazzer fuzzing engine to make it
capable of detecting remote JNDI lookups. We have awarded Code Intelligence $25,000 for this effort and will continue to work with them on securing the open source ecosystem.
Caption: OSS-Fuzz and Jazzer finding the Log4Shell Vulnerability
Vulnerabilities like Log4Shell are an eye-opener for the industry in terms of new attack vectors. With OSS-Fuzz and Jazzer, we can now detect this class of vulnerability so that they can be fixed before they become a problem in production code.
Over the past year we have made a number of investments to strengthen the security of critical open source projects, and recently announced our $
10 billion commitment to cybersecurity defense including $100 million to support third-party foundations that manage open source security priorities and help fix vulnerabilities.
We appreciate the maintainers, security engineers and incident responders that are working to mitigate Log4j and make our internet ecosystem safer.
Check out
our documentation to get started using OSS-Fuzz.
Follow
沒有留言 :
張貼留言