mirror of https://github.com/google/oss-fuzz.git
[docs] Change "hundreds of bugs" to "thousands of bugs" :) (#2674)
* [docs] Change "hundreds of bugs" to "thousands of bugs" :) * include AFL crashes too
This commit is contained in:
parent
d8af01c016
commit
40a183b53f
|
@ -2,9 +2,11 @@
|
|||
|
||||
[Fuzz testing](https://en.wikipedia.org/wiki/Fuzz_testing) is a well-known
|
||||
technique for uncovering programming errors in software.
|
||||
Many of these detectable errors, like [buffer overflow](https://en.wikipedia.org/wiki/Buffer_overflow), can have serious security implications. Google has found [hundreds](https://bugs.chromium.org/p/chromium/issues/list?can=1&q=label%3AStability-LibFuzzer+-status%3ADuplicate%2CWontFix) of security vulnerabilities and stability bugs by deploying [guided in-process fuzzing of Chrome components](https://security.googleblog.com/2016/08/guided-in-process-fuzzing-of-chrome.html),
|
||||
Many of these detectable errors, like [buffer overflow](https://en.wikipedia.org/wiki/Buffer_overflow), can have serious security implications. Google has found [thousands] of security vulnerabilities and stability bugs by deploying [guided in-process fuzzing of Chrome components](https://security.googleblog.com/2016/08/guided-in-process-fuzzing-of-chrome.html),
|
||||
and we now want to share that service with the open source community.
|
||||
|
||||
[thousands]: https://bugs.chromium.org/p/chromium/issues/list?q=label%3AStability-LibFuzzer%2CStability-AFL%20-status%3ADuplicate%2CWontFix&can=1
|
||||
|
||||
In cooperation with the [Core Infrastructure Initiative](https://www.coreinfrastructure.org/),
|
||||
OSS-Fuzz aims to make common open source software more secure and stable by
|
||||
combining modern fuzzing techniques with scalable,
|
||||
|
|
|
@ -11,9 +11,11 @@ has_toc: false
|
|||
|
||||
[Fuzz testing](https://en.wikipedia.org/wiki/Fuzz_testing) is a well-known
|
||||
technique for uncovering programming errors in software.
|
||||
Many of these detectable errors, like [buffer overflow](https://en.wikipedia.org/wiki/Buffer_overflow), can have serious security implications. Google has found [hundreds](https://bugs.chromium.org/p/chromium/issues/list?can=1&q=label%3AStability-LibFuzzer+-status%3ADuplicate%2CWontFix) of security vulnerabilities and stability bugs by deploying [guided in-process fuzzing of Chrome components](https://security.googleblog.com/2016/08/guided-in-process-fuzzing-of-chrome.html),
|
||||
Many of these detectable errors, like [buffer overflow](https://en.wikipedia.org/wiki/Buffer_overflow), can have serious security implications. Google has found [thousands] of security vulnerabilities and stability bugs by deploying [guided in-process fuzzing of Chrome components](https://security.googleblog.com/2016/08/guided-in-process-fuzzing-of-chrome.html),
|
||||
and we now want to share that service with the open source community.
|
||||
|
||||
[thousands]: https://bugs.chromium.org/p/chromium/issues/list?q=label%3AStability-LibFuzzer%2CStability-AFL%20-status%3ADuplicate%2CWontFix&can=1
|
||||
|
||||
In cooperation with the [Core Infrastructure Initiative](https://www.coreinfrastructure.org/),
|
||||
OSS-Fuzz aims to make common open source software more secure and stable by
|
||||
combining modern fuzzing techniques with scalable,
|
||||
|
|
Loading…
Reference in New Issue