Issue 45620 in oss-fuzz: elfutils:fuzz-elf-get-sections: Timeout in fuzz-elf-get-sections

Issue 45620 in oss-fuzz: elfutils:fuzz-elf-get-sections: Timeout in fuzz-elf-get-sections

[ClusterFuzz-External via monorail]

Status: New
Owner: ----
CC: elfut...@sourceware.org, da...@adalogics.com, evv...@gmail.com, izzeem@google.com 
Labels: ClusterFuzz Reproducible Engine-libfuzzer OS-Linux Proj-elfutils Reported-2022-03-17
Type: Bug

New issue 45620 by ClusterFuzz-External: elfutils:fuzz-elf-get-sections: Timeout in fuzz-elf-get-sections
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45620

Detailed Report: https://oss-fuzz.com/testcase?key=5416220013232128

Project: elfutils
Fuzzing Engine: libFuzzer
Fuzz Target: fuzz-elf-get-sections
Job Type: libfuzzer_asan_elfutils
Platform Id: linux

Crash Type: Timeout (exceeds 60 secs)
Crash Address: 
Crash State:
  fuzz-elf-get-sections
  
Sanitizer: address (ASAN)

Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_elfutils&range=202203160607:202203161200

Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5416220013232128

Issue filed automatically.

See https://google.github.io/oss-fuzz/advanced-topics/reproducing for instructions to reproduce this bug locally.
When you fix this bug, please
  * mention the fix revision(s).
  * state whether the bug was a short-lived regression or an old bug in any stable releases.
  * add any other useful information.
This information can help downstream consumers.

If you need to contact the OSS-Fuzz team with a question, concern, or any other feedback, please file an issue at https://github.com/google/oss-fuzz/issues. Comments on individual Monorail issues are not monitored.

-- 
You received this message because:
  1. You were specifically CC'd on the issue

You may adjust your notification preferences at:
https://bugs.chromium.org/hosting/settings

Reply to this email to add a comment.

Re: Issue 45620 in oss-fuzz: elfutils:fuzz-elf-get-sections: Timeout in fuzz-elf-get-sections

[Mark Wielaard]

Hi,

On Wed, Mar 16, 2022 at 05:08:04PM -0700, ClusterFuzz-External via monorail via Elfutils-devel wrote:
> Status: New
> Owner: ----
> CC: elfut...@sourceware.org, da...@adalogics.com, evv...@gmail.com, izzeem@google.com 
> Labels: ClusterFuzz Reproducible Engine-libfuzzer OS-Linux Proj-elfutils Reported-2022-03-17
> Type: Bug
> 
> New issue 45620 by ClusterFuzz-External: elfutils:fuzz-elf-get-sections: Timeout in fuzz-elf-get-sections
> https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45620
> 
> Detailed Report: https://oss-fuzz.com/testcase?key=5416220013232128

Again the detailed report seems to require some kind of login.

> Project: elfutils
> Fuzzing Engine: libFuzzer
> Fuzz Target: fuzz-elf-get-sections
> Job Type: libfuzzer_asan_elfutils
> Platform Id: linux
> 
> Crash Type: Timeout (exceeds 60 secs)
> Crash Address: 
> Crash State:
>   fuzz-elf-get-sections
>   
> Sanitizer: address (ASAN)
> 
> Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_elfutils&range=202203160607:202203161200
> 
> Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5416220013232128

This again looks like the previous reported case.
The reproducer is clearly an invalid file without section headers.

Does anybody know what this "fuzz-elf-get-sections" thing is.
It would be good to know the source code if this to understand how to reproduce this report.

Thanks,

Mark

Issue 45620 in oss-fuzz: elfutils:fuzz-elf-get-sections: Timeout in fuzz-elf-get-sections

[ClusterFuzz-External via monorail]

Updates:
	Labels: ClusterFuzz-Verified
	Status: Verified

Comment #1 on issue 45620 by ClusterFuzz-External: elfutils:fuzz-elf-get-sections: Timeout in fuzz-elf-get-sections
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45620#c1

ClusterFuzz testcase 5416220013232128 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_elfutils&range=202203161800:202203170000

If this is incorrect, please file a bug on https://github.com/google/oss-fuzz/issues/new

-- 
You received this message because:
  1. You were specifically CC'd on the issue

You may adjust your notification preferences at:
https://bugs.chromium.org/hosting/settings

Reply to this email to add a comment.