[Java] FuzzIpcStream: Uncaught exception in java.base/java.nio.Bits.reserveMemory
- Linguagem predominante
- Java
- Estrelas
- 94
- Forks
- 152
- Merge médio
- 3d 16h
- PRs com merge (30d)
- 11
Descrição
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.*
Guia de contribuição
Direção de pesquisa
Comece reproduzindo testcase 4599882936090624 com o target FuzzIpcStream, seguindo as instruções de reprodução vinculadas do OSS-Fuzz. Rastreie a falha de java.nio.Bits.reserveMemory e ByteBuffer.allocateDirect e, em seguida, verifique se testcase não produz mais uma uncaught exception.
Escrita pelo modelo de indexação a partir do texto da issue.
Avaliação
- Stack de tecnologia
- java
- Domínio
- data-engineering
- Tipo de issue
- Bug
- Dificuldade
- 4/5
- Tempo estimado
- 3-5 dias
- Status de atividade
- Estagnada
- Clareza
- Precisa de esclarecimento
- Facilidade para iniciantes
- 25/100