Rooba
/
oss-fuzz
mirror of https://github.com/google/oss-fuzz.git
1
1
Fork 0
Code Issues Packages Projects Releases Wiki Activity
oss-fuzz/projects/elfutils/project.yaml

22 lines
415 B
YAML
Raw Normal View History

elfutils/readelf (#6670) * add elfutils/readelf * Update project.yaml Co-authored-by: jonathanmetzman <31354670+jonathanmetzman@users.noreply.github.com>
2021-10-31 17:02:36 +00:00
homepage: "https://sourceware.org/elfutils/"
language: c++
[elfutils] build elfutils more often (#6999) to prevent OSS-Fuzz from reporting bugs that have already been fixed
2021-12-10 16:22:47 +00:00
builds_per_day: 4
[elfutils] make reports public and point OSS-Fuzz to the official mailing list (#7049) https://sourceware.org/bugzilla/show_bug.cgi?id=28715#c9
2021-12-22 15:28:59 +00:00
primary_contact: "elfutils-devel@sourceware.org"
elfutils/readelf (#6670) * add elfutils/readelf * Update project.yaml Co-authored-by: jonathanmetzman <31354670+jonathanmetzman@users.noreply.github.com>
2021-10-31 17:02:36 +00:00
main_repo: "git://sourceware.org/git/elfutils.git"
fuzzing_engines:
- libfuzzer
- afl
- honggfuzz
sanitizers:
- address
[elfutils] bring MSan back (#7460) Now that all the false positives are gone and MSan reports real issues like https://sourceware.org/bugzilla/show_bug.cgi?id=29000 confirmed by Valgrind it should be safe to bring MSan back. It reverts https://github.com/google/oss-fuzz/commit/6e6d6068aee8552ff62053b338767a572cf2dc40
2022-03-28 18:47:26 +00:00
- memory
elfutils/readelf (#6670) * add elfutils/readelf * Update project.yaml Co-authored-by: jonathanmetzman <31354670+jonathanmetzman@users.noreply.github.com>
2021-10-31 17:02:36 +00:00
- undefined
architectures:
- x86_64
[elfutils] turn on i386 (#7000)
2021-12-10 09:39:05 +00:00
- i386
[elfutils] make reports public and point OSS-Fuzz to the official mailing list (#7049) https://sourceware.org/bugzilla/show_bug.cgi?id=28715#c9
2021-12-22 15:28:59 +00:00
view_restrictions: none
[elfutils] start afresh (#6944) The elfutils project was integrated into OSS-Fuzz in https://github.com/google/oss-fuzz/pull/6670 where Dockerfile pointed to a fork of the official repository with a series of patches that were supposed to make it compile on OSS-Fuzz. Apart from that there was a fuzz target that effectively wrapped the readelf utility by applying a patch to its source code. On the whole it worked at the time but I think there are a few issues: 1. It's hard to point OSS-Fuzz to the official repository (because most of the patches touch the build system and they can't always be applied cleanly); 2. It's almost impossible to add new fuzz targets covering other use cases; 3. It's not possible to build fuzz targets without Docker 4. Since the fuzz target mostly wraps the readelf utility it looks more like a CLI tool than a fuzz target. It calls exit when it should just return 0 to let it keep going and so on. This PR should addresses all those issues apart from 4. The fuzz target was just removed and another one was added instead. (It can be added later though but since it isn't exactly maintainable with the build script pointing at the official repository it should probably be rewritten: https://sourceware.org/pipermail/elfutils-devel/2021q4/004295.html) The new fuzz target covers the code that `systemd` uses to parse untrusted data. Currently it can be used to trigger various issues like heap-buffer-overflows and inifinite loops that in theory can bring down coredump processing on machines where systemd-coredump is used by default. Even though those issues were discovered by one of `systemd` fuzz targets I think elfutils bugs should be caught and reported by elfutils fuzz targets.
2021-12-01 11:15:17 +00:00
auto_ccs:
- evverx@gmail.com
[elfutils] make reports public and point OSS-Fuzz to the official mailing list (#7049) https://sourceware.org/bugzilla/show_bug.cgi?id=28715#c9
2021-12-22 15:28:59 +00:00
- izzeem@google.com
elfutils: add myself to project.yaml (#7394)
2022-03-16 22:38:15 +00:00
- david@adalogics.com