[Java] FuzzIpcStream: Uncaught exception in java.base/java.nio.Bits.reserveMemory
- Lingua principale
- Java
- Stelle
- 94
- Fork
- 152
- Merge medio
- 3g 16h
- PR unite (30g)
- 11
Descrizione
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.*
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Inizia riproducendo testcase 4599882936090624 con il target FuzzIpcStream, seguendo le istruzioni di riproduzione di OSS-Fuzz collegate. Traccia il fallimento di java.nio.Bits.reserveMemory e ByteBuffer.allocateDirect, quindi verifica che testcase non produca più un’uncaught exception.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- java
- Ambito
- data-engineering
- Tipo di issue
- Bug
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Ferma
- Chiarezza
- Da chiarire
- Idoneità per principianti
- 25/100