[Java] FuzzIpcFile: Uncaught exception in java.base/java.nio.HeapByteBuffer.<init>
- Dominant language
- Java
- Stars
- 94
- Forks
- 152
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 11
Description
Detailed Report: https://oss-fuzz.com/testcase?key=5015797066498048
Project: arrow-java
Fuzzing Engine: libFuzzer
Fuzz Target: FuzzIpcFile
Job Type: libfuzzer_asan_arrow-java
Platform Id: linux
Crash Type: Uncaught exception
Crash Address:
Crash State:
java.base/java.nio.HeapByteBuffer.
java.base/java.nio.ByteBuffer.allocate
org.apache.arrow.vector.ipc.ArrowFileReader.readSchema
Sanitizer: address (ASAN)
Recommended Security Severity: Low
Crash Revision: https://oss-fuzz.com/revisions?job=libfuzzer_asan_arrow-java&revision=202201300605
Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5015797066498048
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.
This bug is subject to a 90 day disclosure deadline. If 90 days elapse
without an upstream patch, then the bug report will automatically
become visible to the public.
**Reporter**: [Liya Fan](https://issues.apache.org/jira/browse/ARROW-15557) / @liyafan82
**Note**: *This issue was originally created as [ARROW-15557](https://issues.apache.org/jira/browse/ARROW-15557). Please see the [migration documentation](https://github.com/apache/arrow/issues/14542) for further details.*
Contributor guide
Research direction
Start with the OSS-Fuzz reproducing instructions and testcase 5015797066498048, then inspect org.apache.arrow.vector.ipc.ArrowFileReader.readSchema and the HeapByteBuffer allocation in the crash stack. Reproduce the failure locally and trace the input handling around schema reading. Done means the testcase no longer causes an uncaught exception.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- data
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100