jakartaee / jakartaee/jsonp-api
OSS-Fuzz integration
- Dominant language
- Java
- Stars
- 160
- Forks
- 64
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 4
Description
Hi all,
we have integrated jsonp-api into Google [OSS-Fuzz](https://github.com/google/oss-fuzz) which will provide more security for your project: https://github.com/google/oss-fuzz/pull/9847
**Why do you need Fuzzing?**
The Code Intelligence JVM fuzzer [Jazzer](https://github.com/CodeIntelligenceTesting/jazzer) has already found [hundreds of bugs](https://github.com/CodeIntelligenceTesting/jazzer/blob/main/docs/findings.md) in open source projects including for example [OpenJDK](https://nvd.nist.gov/vuln/detail/CVE-2022-21360), [Protobuf](https://nvd.nist.gov/vuln/detail/CVE-2022-21360) or [jsoup](https://github.com/jhy/jsoup/security/advisories/GHSA-m72m-mhq2-9p6c). Fuzzing proved to be very effective having no false positives. It provides a crashing input which helps you to reproduce and debug any finding easily. The integration of your project into the OSS-Fuzz platform will enable continuous fuzzing of your project by Jazzer.
**What do you need to do?**
The integration requires the maintainer or one established project commiter to deal with the bug reports.
You need to create or provide one email address that is associated with a google account as per [here](https://google.github.io/oss-fuzz/getting-started/accepting-new-projects/). When a bug is found, you will receive an email that will provide you with access to ClusterFuzz, crash reports, code coverage reports and fuzzer statistics. More than 1 person can be included.
**How Code Intelligence can support?**
We will continue to add more fuzz targets to improve code coverage over time. Furthermore, we are permanently enhancing fuzzing technologies by developing new fuzzers and more bug detectors.
Please let me know if you have any questions regarding fuzzing or the OSS-Fuzz integration.
Contributor guide
Research direction
Start with the linked OSS-Fuzz pull request 9847 and the OSS-Fuzz accepting-new-projects guide. Confirm the integration details with the maintainers, provide a Google-associated email for bug reports, and ensure someone is prepared to handle ClusterFuzz findings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- security, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100