commit	cb2ecc10a9f29f1ef06c97eca115f939b4a4c35c	[log] [tgz]
author	Nima Fatemi <mrphs@riseup.net>	Fri Dec 02 01:12:31 2016 +0000
committer	Oliver Chang <oliverchang@users.noreply.github.com>	Thu Dec 01 17:12:31 2016 -0800
tree	e723324e56bedeac5bc6c4a8d5bc6ecd1a10f274
parent	4ca0fc40354fd00001443a717e86d4e3a2354f05 [diff]

tree: e723324e56bedeac5bc6c4a8d5bc6ecd1a10f274

README.md

OSS-Fuzz - Continuous Fuzzing for Open Source Software

Status: Beta. We are preparing the project for public release soon.

Create New Issue for questions or feedback about OSS-Fuzz.

Introduction

Fuzz testing is a well-known technique for uncovering various kinds of programming errors in software. Many of these detectable errors (e.g. buffer overflow) can have serious security implications.

We successfully deployed guided in-process fuzzing of Chrome components and found hundreds of security vulnerabilities and stability bugs. We now want to share the experience and the service with the open source community.

In cooperation with the Core Infrastructure Initiative, OSS-Fuzz aims to make common open source software more secure and stable by combining modern fuzzing techniques and scalable distributed execution.

At the first stage of the project we use libFuzzer with Sanitizers. More fuzzing engines will be added later. ClusterFuzz provides distributed fuzzer execution environment and reporting.

Process Overview

The following process is used for projects in OSS-Fuzz:

A maintainer of an opensource project or an outside volunteer creates one or more fuzz targets and integrates them with the project's build and test system.
These fuzz targets are accepted to OSS-Fuzz.
When ClusterFuzz finds a bug, an issue is automatically reported in the OSS-Fuzz issue tracker (example). (Why different tracker?). Project owners are CC-ed to the bug report.
The bug is fixed upstream.
ClusterFuzz automatically verifies the fix, adds a comment and closes the issue (example).
7 days after the fix is verified or 90 days after reporting, the issue becomes public (guidelines).

Accepting New Projects

To be accepted to OSS-Fuzz, an open-source project must have a significant user base and/or be critical to the global IT infrastructure. To submit a new project:

Create a pull request with new projects/<project_name>/project.yaml file (example) giving at least the following information:
- project homepage.
- e-mail of the engineering contact person to be CCed on new issues. This email should be
  linked to a Google Account
  and belong to an established project committer (according to VCS logs). If this is not you or the email address differs from VCS, an informal e-mail verification will be required.
- Note that project_name can only contain alphanumeric characters, underscores(_) or dashes(-).
Once accepted by an OSS-Fuzz project member, follow the New Project Guide to write the code.

Bug Disclosure Guidelines

Following Google's standard disclosure policy OSS-Fuzz will adhere to following disclosure principles:

90-day deadline. After notifying project authors, we will open reported issues in 90 days, or 7 days after the fix is released.
Weekends and holidays. If a deadline is due to expire on a weekend or US public holiday, the deadline will be moved to the next normal work day.
Grace period. We have a 14-day grace period. If a 90-day deadline expires but the upstream engineers let us know before the deadline that a patch is scheduled for release on a specific day within 14 days following the deadline, the public disclosure will be delayed until the availability of the patch.

OSS-Fuzz - Continuous Fuzzing for Open Source Software

Introduction

Process Overview

Accepting New Projects

Bug Disclosure Guidelines

More Documentation

Build Status

Trophies

References