Error if using negative length in str() and buf() #1621
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
3 tasks
mmisono
added
the
do-not-merge
mmisono
added a commit
to mmisono/bpftrace
that referenced
this pull request
Nov 17, 2020
LibFuzzer is a coverage-guided fuzzer developed with llvm/clang. LibFuzzer's main target is a function, and the biggest difference between AFL and the libfuzzer is that the former re-executes the program after each execution (actually it does fork), while the libFuzzer keeps calling the target function in the main loop. The main target of the libfuzzer is a function, but with a few changes, it can be fuzzed from the beginning of the program, like the AFL. Because the current bpftrace is known to have memory leaks and there might be probably some global states, it may not be suitable for libfuzzer. But libFuzzer already found several bugs (bpftrace#1618, bpftrace#1621). Also, it seems oss-fuzz expects the libfuzzer interface, so support it is a good thing.
fbs
requested changes
Nov 18, 2020
mmisono
added a commit
to mmisono/bpftrace
that referenced
this pull request
Nov 18, 2020
LibFuzzer is a coverage-guided fuzzer developed with llvm/clang. LibFuzzer's main target is a function, and the biggest difference between AFL and the libfuzzer is that the former re-executes the program after each execution (actually it does fork), while the libFuzzer keeps calling the target function in the main loop. The main target of the libfuzzer is a function, but with a few changes, it can be fuzzed from the beginning of the program, like the AFL. Because the current bpftrace is known to have memory leaks and there might be probably some global states, it may not be suitable for libfuzzer. But libFuzzer already found several bugs (bpftrace#1618, bpftrace#1621). Also, it seems oss-fuzz expects the libfuzzer interface, so support it is a good thing.
mmisono
added a commit
to mmisono/bpftrace
that referenced
this pull request
Nov 18, 2020
LibFuzzer is a coverage-guided fuzzer developed with llvm/clang. LibFuzzer's main target is a function, and the biggest difference between AFL and the libfuzzer is that the former re-executes the program after each execution (actually it does fork), while the libFuzzer keeps calling the target function in the main loop. The main target of the libfuzzer is a function, but with a few changes, it can be fuzzed from the beginning of the program, like the AFL. Because the current bpftrace is known to have memory leaks and there might be probably some global states, it may not be suitable for libfuzzer. But libFuzzer already found several bugs (bpftrace#1618, bpftrace#1621). Also, it seems oss-fuzz expects the libfuzzer interface, so support it is a good thing.
mmisono
force-pushed
the
fix_negative_length2
branch
from
77db219
to
cfbf9d4
Compare
fbs
approved these changes
Nov 18, 2020
mmisono
force-pushed
the
fix_negative_length2
branch
from
cfbf9d4
to
76b4cfd
Compare
mmisono
removed
the
do-not-merge
mmisono
added a commit
to mmisono/bpftrace
that referenced
this pull request
Nov 20, 2020
LibFuzzer is a coverage-guided fuzzer developed with llvm/clang. LibFuzzer's main target is a function, and the biggest difference between AFL and the libfuzzer is that the former re-executes the program after each execution (actually it does fork), while the libFuzzer keeps calling the target function in the main loop. The main target of the libfuzzer is a function, but with a few changes, it can be fuzzed from the beginning of the program, like the AFL. Because the current bpftrace is known to have memory leaks and there might be probably some global states, it may not be suitable for libfuzzer. But libFuzzer already found several bugs (bpftrace#1618, bpftrace#1621). Also, it seems oss-fuzz expects the libfuzzer interface, so support it is a good thing.
fbs
pushed a commit
that referenced
this pull request
Nov 23, 2020
LibFuzzer is a coverage-guided fuzzer developed with llvm/clang. LibFuzzer's main target is a function, and the biggest difference between AFL and the libfuzzer is that the former re-executes the program after each execution (actually it does fork), while the libFuzzer keeps calling the target function in the main loop. The main target of the libfuzzer is a function, but with a few changes, it can be fuzzed from the beginning of the program, like the AFL. Because the current bpftrace is known to have memory leaks and there might be probably some global states, it may not be suitable for libfuzzer. But libFuzzer already found several bugs (#1618, #1621). Also, it seems oss-fuzz expects the libfuzzer interface, so support it is a good thing.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This disables a negative length in
str()andbuf(), such asbuf("aaa", -1).Checklist
docs/reference_guide.mdCHANGELOG.md