[Java] FuzzIpcStream: Uncaught exception in java.base/java.nio.Buffer.createCapacityException
- Dominant language
- Java
- Stars
- 94
- Forks
- 152
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 11
Description
Detailed Report: https://oss-fuzz.com/testcase?key=5095153130405888
Project: arrow-java
Fuzzing Engine: libFuzzer
Fuzz Target: FuzzIpcStream
Job Type: libfuzzer_asan_arrow-java
Platform Id: linux
Crash Type: Uncaught exception
Crash Address:
Crash State:
java.base/java.nio.Buffer.createCapacityException
java.base/java.nio.ByteBuffer.allocate
org.apache.arrow.vector.ipc.message.MessageSerializer.readMessage
Sanitizer: address (ASAN)
Crash Revision: https://oss-fuzz.com/revisions?job=libfuzzer_asan_arrow-java&revision=202201300605
Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5095153130405888
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-15560) / @liyafan82
**Note**: *This issue was originally created as [ARROW-15560](https://issues.apache.org/jira/browse/ARROW-15560). Please see the [migration documentation](https://github.com/apache/arrow/issues/14542) for further details.*
Contributor guide
Research direction
Start with org.apache.arrow.vector.ipc.message.MessageSerializer.readMessage and reproduce the FuzzIpcStream crash using testcase 5095153130405888 and the OSS-Fuzz reproduction guidance. Trace the reported ByteBuffer.allocate failure and verify that the supplied testcase no longer produces an uncaught exception.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- data-engineering
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100