[Java] FuzzIpcStream: Uncaught exception in java.base/java.nio.Bits.reserveMemory
- Vorherrschende Sprache
- Java
- Sterne
- 94
- Forks
- 152
- Ø Merge
- 3 T. 16 Std.
- Gemergte PRs (30 T.)
- 11
Beschreibung
Detailed Report:
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.Bits.reserveMemory
java.base/java.nio.DirectByteBuffer.
java.base/java.nio.ByteBuffer.allocateDirect
Sanitizer: address (ASAN)
Recommended Security Severity: Low
Crash Revision:
Reproducer Testcase:
Issue filed automatically.
See 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 . 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-15562) / @liyafan82
**Note**: *This issue was originally created as [ARROW-15562](https://issues.apache.org/jira/browse/ARROW-15562). Please see the [migration documentation](https://github.com/apache/arrow/issues/14542) for further details.*
Beitragsleitfaden
Rechercherichtung
Beginne damit, testcase 4599882936090624 mit dem Ziel FuzzIpcStream zu reproduzieren, und befolge dabei die verlinkten Reproduktionsanweisungen von OSS-Fuzz. Verfolge den Fehler von java.nio.Bits.reserveMemory und ByteBuffer.allocateDirect und überprüfe anschließend, dass testcase keine uncaught exception mehr erzeugt.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- java
- Bereich
- data-engineering
- Issue-Typ
- Bug
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Muss geklärt werden
- Anfängerfreundlichkeit
- 25/100