Skip to content

Commit e3291c1

Browse files
committed
examples: Fix Log4jFuzzer definition
The fuzzer still finds the issue in ~2-3 minutes as verified manually.
1 parent fb22ffa commit e3291c1

File tree

1 file changed

+6
-1
lines changed

1 file changed

+6
-1
lines changed

examples/BUILD.bazel

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -167,14 +167,19 @@ java_fuzz_target_test(
167167
srcs = [
168168
"src/main/java/com/example/Log4jFuzzer.java",
169169
],
170+
allowed_findings = ["com.code_intelligence.jazzer.api.FuzzerSecurityIssueCritical"],
170171
fuzzer_args = [
171172
"-fork=4",
172173
"-use_value_profile=1",
173174
],
174175
# Finding this bug takes ~5 minutes on a decent laptop, but the GitHub Actions machines are not
175176
# powerful enough to run it as part of our test suite.
176-
tags = ["manual"],
177+
tags = [
178+
"cpu:4",
179+
"manual",
180+
],
177181
target_class = "com.example.Log4jFuzzer",
182+
verify_crash_reproducer = False,
178183
deps = [
179184
"@maven//:org_apache_logging_log4j_log4j_api",
180185
"@maven//:org_apache_logging_log4j_log4j_core",

0 commit comments

Comments
 (0)